Bump the Elasticsearch client gem to version 7.10.x.#3548
Open
Bump the Elasticsearch client gem to version 7.10.x.#3548
Conversation
We’re planning an upcoming upgrade of our cluster to 7.10, so this change allows us to adopt the newer client early and ensure the codebase remains compatible.
This filter is deprecated, as it no longer provides any functional behavior. https://stackoverflow.com/questions/76108163/getting-error-the-standard-token-filter-has-been-removed-when-running-a-que
…7.10 client. The Elasticsearch client gem has been updated and now issues POST requests for search operations instead of GET.
When updating a mapping, the Elasticsearch client may now use either
of the following endpoint formats:
$HOSTNAME/{index}/_mapping/{type}
$HOSTNAME/{index}/{type}/_mappings
Both URL patterns are supported by Elasticsearch 6.8.
… client.
When performing a scroll search, the Elasticsearch client may now use
either of the following endpoint formats:
$HOSTNAME/_search/scroll/{scroll_id}?scroll=1m
$HOSTNAME/_search/scroll?scroll=1m&scroll_id={scroll_id}
Both URL patterns are supported by Elasticsearch 6.8.
Although _uid is still present in Elasticsearch 6.8, it is deprecated. All usages have been updated to _id to ensure forward compatibility with future Elasticsearch versions. Reference: https://www.elastic.co/guide/en/elasticsearch/reference/6.8/mapping-uid-field.html
Use a fallback when doc['popularity'] is empty by applying POPULARITY_OFFSET directly; otherwise add the offset to the existing value. This is necessary because Elasticsearch 7+ requires the property to exist if accessed popularity data is missing.
Elasticsearch 7+ does not allow nested 'should' queries
Contributor
|
This looks good based on my reading of the docs, but it will be interesting to see how it fares on integration as it's hard to know for sure if we've missed anything! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bump the Elasticsearch client gem to version 7.10.x.
We’re planning an upcoming upgrade of our cluster to 7.10, so this
change allows us to adopt the newer client early and ensure the codebase
remains compatible.
https://gov-uk.atlassian.net/browse/SCH-1868