-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat: Add Elasticsearch 7 support #2092
feat: Add Elasticsearch 7 support #2092
Conversation
Some parameters in search query are optional and automatically populated. With the ES upgrade these parameters could be removed/added.
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 picking this up!
@@ -22,18 +22,17 @@ | |||
"fuzzy_transpositions" : true, | |||
"lenient" : false, | |||
"zero_terms_query" : "NONE", | |||
"auto_generate_synonyms_phrase_query": true, |
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.
Similar question: what is the default value for this?
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.
(Optional, Boolean) If true, match phrase queries are automatically created for multi-term synonyms. Defaults to true. See Synonyms for an example.
I don't know why this was added, I copied it from Jyoti's PR. I can remove it and see what happens?
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.
Ah, this is in test data. Yes, I'm guessing the ES java library makes some defaults explicit.
fyi @cobolbaby |
* upgrade to ES7 * add doc summarizing the changes * Call out the optional parameters in search query Some parameters in search query are optional and automatically populated. With the ES upgrade these parameters could be removed/added. * revert unrelated changes * update required max_ngram_diff field for ES7 (caught by integration tests) Co-authored-by: Jyoti Wadhwani <[email protected]>
Taking over from https://github.com/linkedin/datahub/pull/1997/files
This is now tested with the integration test framework :)
Checklist