-
Notifications
You must be signed in to change notification settings - Fork 165
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
Setup Lucene document threshold at query time #5149
Comments
I'll have to take a look at the code to understand how things are handled at the moment. |
Any news on what to do? |
For this code we can probably allow the number of rows to be set on the query before this method is called. Something like |
Looks like this here is where we extract variables from the SPARQL query: rdf4j/core/sail/lucene-api/src/main/java/org/eclipse/rdf4j/sail/lucene/QuerySpecBuilder.java Line 450 in 755a631
So that can be extended to add |
We can't do the same with Same for |
…s param in LuceneSail query
…s param in LuceneSail query
…s param in LuceneSail query
@hmottestad do you think you can get a look at how I have implemented it in the PR #5163? |
Thanks for the reminder :) |
…KEY and MAX_DOCUMENTS_KEY to DEFAULT_NUM_DOCS_KEY
…KEY and MAX_DOCUMENTS_KEY to DEFAULT_NUM_DOCS_KEY
Problem description
Inside the LuceneSail, an option exists to tell what is the amount of documents to retrieve. It is set with the property
maxDocuments
during the sail init and can't be set at runtime. We would need an option to allow this.Preferred solution
An option would be to add a virtual predicate during query time like
search:maxDocuments
with a property during init to enable or disable it, maybeallowQueryMaxDocument
.My main concern is to implement it. The maxDocuments values is used inside each index implementation.
So the different methods will need to have a max documents param. I would like an opinion on it before implementing it.
Are you interested in contributing a solution yourself?
Yes
Alternatives you've considered
No response
Anything else?
ec-doris/kohesio-backend#268
The text was updated successfully, but these errors were encountered: