Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
SAI-4737: System prop
solr.MaxBasicQueriesOverride
for surround query #172SAI-4737: System prop
solr.MaxBasicQueriesOverride
for surround query #172Changes from 3 commits
748787a
43bde54
27232ba
cd19bc0
3495cdc
c0ceec7
4102f3c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
How about just setting value, if that is positive. Probably we don't need to log here.
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 current logic basically only considers "solr.absoluteMaxBasicQueries" if it was provided and positive. Pretty similar to what your are suggesting?
Are you suggesting "solr.absoluteMaxBasicQueries" will just override
maxBasicQueries
in all cases? Currently "solr.absoluteMaxBasicQueries" acts as a absolute safeguard,maxBasicQueries
is still effective as far as it stays below "solr.absoluteMaxBasicQueries".The log was mostly to avoid the case that user is confused which a higher
maxBasicQueries
seems to have no impact (because of thesolr.absoluteMaxBasicQueries
). I have some concern that this could be noisy, though once per surround query is probably not too bad imo :) ?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.
log would be per query, per shard ?
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.
It was per query on core I believe.
Since now it's a temporary override (the dev should be well aware of it, unlike the proposal before which could be long living), I have removed the logging :)