1234567891011121314151617181920212223242526272829303132 |
- [float]
- [[breaking_70_restclient_changes]]
- === High-level REST client changes
- [float]
- ==== API methods accepting `Header` argument have been removed
- All API methods accepting headers as a `Header` varargs argument, deprecated
- since 6.4, have been removed in favour of the newly introduced methods that
- accept instead a `RequestOptions` argument. In case you are not specifying any
- header, e.g. `client.index(indexRequest)` becomes
- `client.index(indexRequest, RequestOptions.DEFAULT)`.
- In case you are specifying headers
- e.g. `client.index(indexRequest, new Header("name" "value"))` becomes
- `client.index(indexRequest, RequestOptions.DEFAULT.toBuilder().addHeader("name", "value").build());`
- [float]
- ==== Cluster Health API default to `cluster` level
- The Cluster Health API used to default to `shards` level to ease migration
- from transport client that doesn't support the `level` parameter and always
- returns information including indices and shards details. The level default
- value has been aligned with the Elasticsearch default level: `cluster`.
- === Low-level REST client changes
- [float]
- ==== Support for `maxRetryTimeout` removed from RestClient
- `RestClient` and `RestClientBuilder` no longer support the `maxRetryTimeout`
- setting. The setting was removed as its counting mechanism was not accurate
- and caused issues while adding little value.
|