Implement interactive transactions
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 43
- Forks
- 17
- Avg merge
- 28m
- Merged PRs (30d)
- 2
Description
Interactive transactions have made it into the core recently. They allow us to open a transaction and do selects/updates with yield. I suggest that we add support for them to crud.
Unfortunately, we won't get multi-node transactions, but since we have an understanding of which shard the operation will go to, we can still allow transactional operations if they touch only one storage.
This should be pretty easy to implement: if we open a transaction, record which node the first operation goes to, then make sure all other operations in the transaction go to the same node. If not, abort the operation or the whole transaction.
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the existing CRUD operation paths and the core interactive transaction API to understand how transactions and shard selection are represented. Trace how the first operation identifies a node, then define and test the behavior when later operations target another node, including whether to abort that operation or the whole transaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- backend, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100