lance-format / lance-format/lance
Use u64 for lance-io reader byte ranges
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
PR #6356 only fixes the immediate write-path review comment by keeping external blob logical offsets/sizes as u64 in blob.rs.
We still expose usize-based byte ranges in lance-io (Reader, WriteExt::copy_range_from_reader, ObjectStore::open_with_size, and the file+uring readers). That means large offsets on 32-bit platforms still cannot be expressed end-to-end without lossy downcasts at the I/O boundary.
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
Start with PR #6356 and blob.rs, then trace the lance-io Reader, WriteExt::copy_range_from_reader, ObjectStore::open_with_size, and file+uring readers named in the issue. Done means byte ranges remain expressible as u64 end-to-end, including on 32-bit platforms, without lossy I/O-boundary downcasts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100