-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
SOLR-14036: Remove explicit distrib=false from /terms handler #1900
Conversation
munendrasn
commented
Sep 21, 2020
- This removes shards, shards.qt, and shard whitelisting checks from TermsComponent. Similar to other components, this check will be done in HttpShardHandler
@tflobbe I have removed CustomTermsComponentTest as none of the components currently have custom handling of shardWhitelist. Let me know if that should be added back |
I'm glad to see this :-) I think the change of default behavior for users using /terms should be master-only and have a note in |
@joel-bernstein Please review(not able to tags as a reviewer so the ping) |
At this point, I'm planning to keep this master only but if there is a need will backport the necessary changes to 8x |
I can't comment on the code, as I did not understand the shard part. I am happy if the extra parameter (distrib=false) is not needed. I did feel that maybe a test was missing somehow. Is there one that tests that distributed terms work? Especially, since terms handler is explicitly defining the Component Chain to be terms only and nothing else (not even sure if that's relevant, though). |
@arafalov |
Thank you for clarification. I saw that code change, but did not realize it answered my question. |
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.
Once I see the solr-upgrade-notes.adoc change, I'll approve.
* cleanup shards parameter handling in TermsComponent. This is handled in HttpShardHandler
69aa0b8
to
8bc85c0
Compare
I have included the changes and upgrade entry. Instead of adding upgrade entry to |
Co-authored-by: David Smiley <david.w.smiley@gmail.com>