lance-format / lance-format/lance
2.0 failing with forced binary compression of fsst
Open
Nobody has claimed this yet.
A-encoding
enhancement
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
Unclear if this is a regression but it is fixable. The 2.0 encoding should not panic if the compression is set to fsst and the data type is binary.
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 Lance 2.0 encoding path that handles forced fsst compression and binary data. Reproduce the panic with binary input and fsst selected, then verify that encoding completes without panicking for that combination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100