-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
duckdb blocking #179
duckdb blocking #179
Conversation
nomenklatura/index/duckdb_index.py
Outdated
query = """ | ||
SELECT field, token, id, frequency | ||
FROM frequencies | ||
ORDER by field, token |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit weird, but: is there a world where we want to do ORDER BY frequency DESC OFFSET 1000
(or OFFSET 1%) here to basically take out stopword tokens?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this, but are you happy for me to park the idea for a while and come back to it in the future? It feels lik a basic xref improvment and some other things are higher prio and this might need some experimentation
By letting it materialise intermediate results more explicitly instead of doing multiple joins concurrently
Duckdb bulk enricher
No description provided.