Use query param instead of a system property for opting in for new cluster health response code#79351

Merged

arteam merged 20 commits intoelastic:masterfrom arteam:query-param-instead-of-setting

Oct 18, 2021

+112-58

Commits on Oct 18, 2021

Use query param instead of a system property for opting in for new cluster health response code
arteam
committed
Merge branch 'master' into query-param-instead-of-setting
elasticmachine
authored
Use version 8
arteam
committed
Update server/src/main/java/org/elasticsearch/action/admin/cluster/health/ClusterHealthResponse.java

arteam
and
DaveCTurner
authored
Throw an error if user requests 200 on an older cluster
arteam
committed
Remove the constructor with a single return200ForServerTimeout
arteam
committed
Add query parameter to the docs
arteam
committed
Don't send return200ForClusterHealthTimeout to older nodes
arteam
committed
Don't follow JavaBeans conventions
arteam
committed
Update x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/ml/utils/MlIndexAndAliasTests.java

arteam
and
DaveCTurner
authored
Update server/src/main/java/org/elasticsearch/rest/action/admin/cluster/RestClusterHealthAction.java

arteam
and
DaveCTurner
authored
Add an integration test for sending return_200_for_cluster_health_timeout query parameter
arteam
committed
Set the correct query parameter name ("return_200_for_cluster_health_timeout")
arteam
committed
Merge branch 'master' into query-param-instead-of-setting
elasticmachine
authored
Add Strings import
arteam
committed
Merge branch 'master' into query-param-instead-of-setting
elasticmachine
authored
Merge branch 'master' into query-param-instead-of-setting
elasticmachine
authored
Skip "cluster health request timeout with 200 response code" test for BWC
arteam
committed
Merge branch 'master' into query-param-instead-of-setting
elasticmachine
authored
Update 20_request_timeout.yml test name with bwc and backport for 7.16
arteam
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Use query param instead of a system property for opting in for new cluster health response code#79351

Commits on Oct 18, 2021

Use query param instead of a system property for opting in for new cluster health response code

Merge branch 'master' into query-param-instead-of-setting

Use version 8

Update server/src/main/java/org/elasticsearch/action/admin/cluster/health/ClusterHealthResponse.java

Throw an error if user requests 200 on an older cluster

Remove the constructor with a single return200ForServerTimeout

Add query parameter to the docs

Don't send return200ForClusterHealthTimeout to older nodes

Don't follow JavaBeans conventions

Update x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/ml/utils/MlIndexAndAliasTests.java

Update server/src/main/java/org/elasticsearch/rest/action/admin/cluster/RestClusterHealthAction.java

Add an integration test for sending return_200_for_cluster_health_timeout query parameter

Set the correct query parameter name ("return_200_for_cluster_health_timeout")

Merge branch 'master' into query-param-instead-of-setting

Add Strings import

Merge branch 'master' into query-param-instead-of-setting

Merge branch 'master' into query-param-instead-of-setting

Skip "cluster health request timeout with 200 response code" test for BWC

Merge branch 'master' into query-param-instead-of-setting

Update 20_request_timeout.yml test name with bwc and backport for 7.16