lance-format / lance-format/lance
It is not obvious, from analyze_plan output, how many rows are covered by the index
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
I was recently debugging a performance issue where the FilteredRead was very slow even though a scalar index was applied. It turns out the index was not updated (less than half the rows were covered by the index). It was not obvious from the analyze plan output that this was the problem and it should be something we can easily report.
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 locating the analyze_plan implementation and the FilteredRead path that uses the scalar index. Inspect how the plan currently reports index information, then determine how to expose the number or proportion of rows covered; done means analyze_plan makes incomplete index coverage apparent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100