Transactionality and Rollback
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
Once we have Atomic updates we need to look at implementing transactionality/roll back functionality - this is very important for batch updates such as the load from parquet and batch updates in graphql.
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
Read the Atomic updates implementation first, then trace the batch-update paths for parquet loads and GraphQL. Define the rollback behavior and verify that both batch cases recover consistently; the issue does not name files or tests, so the relevant entry points must be located in the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100