lance-format / lance-format/lance
The k value in top_k is too large, or the k value in limit k is too large, causing the task to core dump directly.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
If Lance is used as the underlying storage format in a commercialized product, when facing large tables, customers do not pay attention to memory usage during arbitrary queries, nor do they deliberately consider whether the k value might blow up the current memory. Directly core dumping the task is not very user‑friendly. I wonder if there could be some protective measures to gracefully inform the user with actionable information and then exit the task.
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 reproducing a query against a large Lance table with an oversized top_k or limit k value, then inspect where the task core dumps. The issue is done when the same input exits gracefully with actionable information instead of crashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100