v9.0.0
Ruby 3.2 and up are tested and supported for 9.0. Older versions of Ruby have reached their end of life. We follow Ruby’s own maintenance policy and officially support all currently maintained versions per Ruby Maintenance Branches. The required Ruby version is set to 2.6 to keep compatiblity wit JRuby 9.3. However, we only test the code against currently supported Ruby versions.
Gem
The size of both elasticsearch and elasticsearch-api gems is smaller than in previous versions. Some unnecessary files that were being included in the gem have now been removed. There has also been a lot of old code cleanup for the 9.x branch.
Elasticsearch Serverless
With the release of 9.0, the Elasticsearch Serverless client has been discontinued. You can use this client to build your Elasticsearch Serverless Ruby applications. The Elasticsearch Serverless API is fully supported. The CI build for Elasticsearch Ruby runs tests to ensure compatibility with Elasticsearch Serverless.
Elasticsearch API
- The source code is now generated from
elasticsearch-specification, so the API documentation is much more detailed and extensive. The valueElasticsearch::ES_SPECIFICATION_COMMITis updated with the commit hash of elasticsearch-specification in which the code is based every time it's generated. - The API code has been updated for compatibility with Elasticsearch API v 9.0.
indices.get_field_mapping-:fieldsis a required parameter.knn_search- This API has been removed. It was only ever experimental and was deprecated in v8.4. It isn't supported in 9.0, and only works when the headercompatible-with=8is set. The search API should be used for all knn queries.- The functions in
utils.rbthat had names starting with double underscore have been renamed to remove these (e.g.__listifytolistify). - Namespaces clean up: The API namespaces are now generated dynamically based on the elasticsearch-specification. As such, some deprecated namespace files have been removed from the codebase:
- The
rollupnamespace was removed. The rollup feature was never GA-ed, it has been deprecated since8.11.0in favor of downsampling. - The
data_frame_deprecated,remotenamespace files have been removed, no APIs were available. - The
shutdownnamespace was removed. It is designed for indirect use by ECE/ESS and ECK. Direct use is not supported.
- The
Scroll APIs need to send scroll_id in request body
Sending the scroll_id as a parameter has been deprecated since version 7.0.0. It needs to be specified in the request body for clear_scroll and scroll.
Impact
Client code using clear_scroll or scroll APIs and the deprecated scroll_id as a parameter needs to be updated.
Action
If you are using the clear_scroll or scroll APIs, and sending the scroll_id as a parameter, you need to update your code to send the scroll_id as part of the request body:
# Before:
client.clear_scroll(scroll_id: scroll_id)
# Now:
client.clear_scroll(body: { scroll_id: scroll_id })
# Before:
client.scroll(scroll_id: scroll_id)
# Now:
client.scroll(body: { scroll_id: scroll_id })Testing
The gem elasticsearch-api migrated away from the Elasticsearch REST API tests and test runner in CI. We now run the Elasticsearch Client tests with the Elasticsearch Tests Runner. This gives us more control on what we're testing and makes the Buildkite build way faster in Pull Requests and scheduled builds.
Fixes
- Some old rake tasks that were not being used have been removed. The rest were streamlined, the
esnamespace has been streamlined to make it easier to run Elasticsearch with Docker during development. Thedockertask namespace was merged intoes. - Elasticsearch's REST API Spec tests can still be ran with
rake test:deprecated:rest_apiand setting the corresponding value for the environment variableTEST_SUITE('platinum' or 'free').