[DOCS] Fixes breaking changes for low level client (#39930)
This commit is contained in:
parent
7c7933b0aa
commit
ea16015bc4
|
@ -2,6 +2,13 @@
|
|||
[[breaking_70_low_level_restclient_changes]]
|
||||
=== 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.
|
||||
|
||||
[float]
|
||||
==== Deprecated flavors of performRequest have been removed
|
||||
|
||||
|
|
|
@ -21,12 +21,3 @@ 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.
|
Loading…
Reference in New Issue