posit-dev / posit-dev/raghilda
Use new NEAREST BY joins duckdb feature
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 36
- Forks
- 0
- Avg merge
- 17m
- Merged PRs (30d)
- 3
Description
We can expose some interesting retrieval patterns and likely reduce some internal code volume by taking advantage of the new NEAREST BY join keyword.
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 DuckDB NEAREST BY join proposal at https://github.com/duckdb/duckdb/pull/24137, then inspect raghilda's retrieval patterns and internal code that could use it. Done means the relevant retrieval patterns are exposed with the new join and the duplicated internal code is reduced, with the existing tests still passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100