Optimistic concurrency control
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 34.7k
- Forks
- 2.7k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 187
Description
Is your feature request related to a problem? Please describe.
Optimistic concurrency control would
- allow detecting and aborting stale payload updates from our application
- improve indexing throughput by enabling multiple writers to upsert the same point and retain consistency with the source.
Describe the solution you'd like
Search operations return a sequence number per point. This sequence number could be used in an upsert/delete request which would abort the mutation if the request's sequence number is stale.
Describe alternatives you've considered
We currently have to accept that updating the the payload of a point concurrently will result in silently lost updates.
Additional context
As an example, see OCC in ElasticSearch.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing search, upsert, and delete APIs, along with the linked Elasticsearch optimistic concurrency control reference. Define how returned per-point sequence numbers are supplied to mutations and how stale upsert or delete requests abort. Done means concurrent writers cannot silently overwrite newer payload updates and the behavior is covered by the relevant API tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100