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
Enhancement/terms lookup fixes #12870
Conversation
* @deprecated use [bool] query instead | ||
*/ | ||
@Deprecated | ||
public TermsQueryBuilder disableCoord(boolean disableCoord) { |
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.
Thanks for doing this, can you also make the parser use a ParseField that marks it as deprecated?
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.
good point, done
86dce9a
to
f8986b4
Compare
LGTM |
TermsQueryParser doesn't support the cache field anymore, so if it gets set through java api, the subsequent parsing of that query will throw error
…TermsQueryBuilder TermsQueryParser still parses those values although deprecated. These need to be present in the java api as well to get ready for the query refactoring, where the builders are the intermediate query format that we parse our json queries into. Whatever the parser supports need to be supported by the builder as well.
f8986b4
to
64bfbd2
Compare
TermsQueryParser doesn't support the cache field anymore, so if it gets set through java api, the subsequent parsing of that query will throw error Relates to elastic#12870
Marking this as breaking as the removal of the setter for |
Relates to #12042 (comment) .