lance-format / lance-format/lance
range end index out of range for slice after merge
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
There is just only one row in my lance table . I want to add some new columns. I used the dataset's merge function. It seems my execution is OK. But when I came back and used duckdb to select this table, the following error happened.
This is my new column (I am debugging and trying only one column):
Just when the new column str is very short, I can success to merge and select from my table.
My pylance package is 2.0.1
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 the issue with a one-row Lance table, the dataset merge operation, and a long string in the new column, then query the result with DuckDB. Compare it with the short-string case and identify where the range-end error is raised; done means both merged tables can be queried successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100