lance-format / lance-format/lance
column expression parsing always use sql
Open
Nobody has claimed this yet.
performance
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
since all columns names are wrapped with backtics (see: escape_field_path_for_project()), when the names are searched for in Planner::parse_expr() they never match the column names in the schema, and the slower sql code path is used (unnecessarily).
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 tracing escape_field_path_for_project() into Planner::parse_expr() and compare the escaped column names with the schema names used during lookup. Verify the affected expression cases and confirm that matching columns no longer fall through to the slower SQL path; add or update regression coverage if the repository provides a relevant test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100