| Title (Goal) | ore:aggregation locking |
|---|---|
| Primary Actor | |
| Scope | |
| Level | |
| Author | Justin Coyne |
| Story (A paragraph or two describing what happens) | The |
...
| ore:aggregation ontology defines a linked-list like structure. However linked lists do not handle concurrent writes gracefully. One actor could update node1.next to be node2 while another actor is trying to update node1.next to be node3. In hydra we are using a distributed lock (redlock) in Redis to prevent these simultaneous mutations. Could an api for dealing with atomic access to ore:aggregations be added? |