Project

General

Profile

Actions

Feature #5960

open

[API] Support transactional update of collections by multiple writers

Added by Peter Amstutz over 9 years ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Story points:
-
Release:
Release relationship:
Auto

Description

To be able to reliably use the fuse mount as a writable shared drive, it is necessary to be able to have multiple writers safely update the collection record.

Currently, there is a race condition whereby one writer may read the collection record, a 2nd writer writes an updated record, then the first writer writes a merged record which is loses the changes from the 2nd writer.

The solution is one of:

1) Implement conditional update of the database record based on PDH or timestamp; in the above scenario, the 2nd write would fail, get the updated record, re-merge and re-write

2) Implement a "merge" method on the API server which takes a list of changes and applies it to the manifest on the server to get a merged manifest.

Actions #1

Updated by Peter Amstutz over 9 years ago

  • Description updated (diff)
Actions #2

Updated by Peter Amstutz over 1 year ago

  • Release set to 60
Actions #3

Updated by Peter Amstutz 7 months ago

  • Target version set to Future
Actions

Also available in: Atom PDF