Bump the Elasticsearch client gem to version 7.10.x. - #3548
Open
koetsier wants to merge 7 commits into
Open
Conversation
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! |
koetsier
force-pushed
the
update_es_client
branch
2 times, most recently
from
April 29, 2026 09:11
2696e45 to
7b43630
Compare
koetsier
marked this pull request as draft
May 7, 2026 13:06
koetsier
force-pushed
the
update_es_client
branch
3 times, most recently
from
June 8, 2026 16:41
16184c9 to
015b0fe
Compare
koetsier
force-pushed
the
update_es_client
branch
5 times, most recently
from
June 12, 2026 10:07
858d095 to
d185bf5
Compare
Elasticsearch 7+ does not allow nested 'should' queries
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. # Conflicts: # spec/unit/elasticsearch_index_spec.rb
koetsier
force-pushed
the
update_es_client
branch
from
June 25, 2026 13:56
d185bf5 to
2dfbca3
Compare
… 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 # Conflicts: # lib/tasks/export.rake
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.
koetsier
force-pushed
the
update_es_client
branch
from
June 25, 2026 14:04
2dfbca3 to
fdb7b72
Compare
koetsier
marked this pull request as ready for review
July 23, 2026 09:40
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