lance-format / lance-format/lance
Create lance-index-core which contains key index types
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
The lance-index crate has grown too large. I think we'd like to eventually move towards a model where each index type is in its own crate. To start this process we should move the core index concepts (traits, common types, etc.) into a lance-index-core crate. This crate should not need to depend on datafusion and, the lance crate we should really depend on would maybe be lance-core for the error/result types.
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 by reviewing the existing lance-index crate and identifying its core index traits and common types. Check how the lance crate currently uses those types and where datafusion and lance-core dependencies enter the design. Done means a new lance-index-core crate contains the shared concepts without depending on datafusion, with the intended crate dependencies updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100