- Ruby Client: other versions:
- Overview
- Getting started
- Installation
- Connecting
- Configuration
- Integrations
- Examples
- Troubleshooting
- Client helpers
- Release Notes
- 8.17 Release notes
- 8.16 Release notes
- 8.15 Release notes
- 8.14 Release notes
- 8.13 Release notes
- 8.12 Release notes
- 8.11 Release notes
- 8.10 Release notes
- 8.9 Release notes
- 8.8 Release notes
- 8.7 Release notes
- 8.6 Release notes
- 8.5 Release notes
- 8.4 Release notes
- 8.3 Release notes
- 8.2 Release notes
- 8.1 Release notes
- 8.0 Release notes
- 7.17 Release notes
- 7.16 Release notes
- 7.15 Release notes
- 7.14 Release notes
- 7.13 Release notes
- 7.12 Release notes
- 7.11 Release notes
- 7.10 Release notes
- 7.9 Release notes
- 7.8 Release notes
- 7.7 Release notes
- 7.6 Release notes
- 7.5 Release notes
- 7.0 Release notes
8.17 Release notes
edit8.17 Release notes
edit8.17.1 Release notes
editClient
edit- Fixes ScrollHelper issue #2556 - There was a bug where an additional search (with scroll) request was made to Elasticsearch for each resulting hit. It was rewritten so that the docs are retrieved as needed and the Helper instance doesn’t store documents internally, with big savings in memory and requests to Elasticsearch.
8.17.0 Release notes
editClient
edit- Tested versions of Ruby for 8.17.0: Ruby (MRI) 3.1, 3.2 and 3.3. JRuby 9.3 and JRuby 9.4.
API
editAPI changes
edit-
async_search.submit
- Removeskeep_alive
parameter. Adds:-
ccs_minimize_roundtrips
(Boolean): When doing a cross-cluster search, setting it to true may improve overall search latency, particularly when searching clusters with a large number of shards. However, when set to true, the progress of searches on the remote clusters will not be received until the search finishes on all clusters. -
rest_total_hits_as_int
(Boolean): Indicates whether hits.total should be rendered as an integer or an object in the rest search response.
-
-
open_point_in_time
- Addsallow_partial_search_results
(Boolean) parameter: Specify whether to tolerate shards missing when creating the point-in-time, or otherwise throw an exception (default: false).
Was this helpful?
Thank you for your feedback.