lance-format / lance-format/lance
[DuckDB] Implement replacement scan function for Lance Scan in DuckDB
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
Problem Statement
DuckDB has a concept of replacement scan when the URL of dataset matches to certain pattern, the URL itself can be used to indicate which scan function to call,
For example,
SELECT * FROM s3://foo/bar/zoo.lance
-- Replace
SELECT * FROM lance_scan("s3://foo/bar/zoo.lance")
Reference of the old (c++) implementation
Desired Behavior
Re-enable the scan replacement of lance scan in the rust-based duckdb extension.
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 comparing the rust-based DuckDB extension with the referenced old C++ implementation at the linked lance-extension.cc location. Trace how the extension registers scan functions and identify the entry point for replacement scans. Done means Lance URLs such as s3://foo/bar/zoo.lance are routed to lance_scan without requiring an explicit function call.
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
- Mostly clear
- Newbie friendliness
- 35/100