batch operations: add `tuple_index` field in error object
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 43
- Forks
- 17
- Avg merge
- 28m
- Merged PRs (30d)
- 2
Description
CRUD can be used by projects written in programming languages
other than lua (at the moment CRUD batch operations are used in tt import).
In this case the format of the tuple from error object and the format of tuple
representation in the application are different. Therefore, it becomes
difficult to understand on which tuple the operation was interrupted.
The solution is to add tuple_index field in error object.
This field should contain index of tuple in original batch.
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 tracing CRUD batch-operation error construction and the tuple handling used by tt import. Check how the error object is exposed to callers and where batch indexes are available. Done means the error object includes the original batch tuple's index so applications can identify the interrupted tuple.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100