lance-format / lance-format/lance
First transaction attempt should error on missing versions when checking for transaction conflicts
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
Currently, there is a special case during transaction conflict resolution to handle read errors due to missing versions and succeed.
This should be removed as the transaction may conflict with old versions which have been cleaned up. The transaction should fail instead.
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 rust/lance/src/io/commit.rs around line 753 and trace the special case for read errors caused by missing versions during transaction conflict resolution. Done means the first transaction attempt reports a conflict when required old versions are missing, rather than succeeding through that special case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 42/100