lance-format / lance-format/lance
[DuckDB] Expose vector search capability via duckdb extension
Open
Nobody has claimed this yet.
A-index
duckdb
good first issue
help wanted
rust
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
Problem Statement
Lance rust dataset has the capability of querying over vector space, via Scannner::nearest(..), we should expose this to DuckDB via its extension mechanism.
For example, a potential implementation could be a duckdb table function lance_nearest
SELECT id, col
FROM lance_nearest("table", "vector_column", "query", top_k)
WHERE city = 'SF' and day = "02-03-2023"
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 reading the Lance Rust dataset vector-search capability through Scanner::nearest(..) and the repository's DuckDB extension integration. Define how a lance_nearest table function would expose the table, vector column, query, top-k, and filtering shown in the example; done means vector queries can run through DuckDB.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100