- Notifications
You must be signed in to change notification settings - Fork 25.5k
Remove cluster state from /_cluster/reroute
response #114231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove cluster state from /_cluster/reroute
response #114231
Conversation
Hi @DaveCTurner, I've created a changelog YAML for you. Note that since this PR is labelled |
Including the cluster state in responses to the `POST _cluster/state` API was deprecated in elastic#90399 (v8.6.0) requiring callers to pass `?metric=none` to avoid the deprecation warning. This commit adjusts the behaviour as promised in v9 so that this API never returns the cluster state, and deprecates the `?metric` parameter itself. Closes elastic#88978
49a36ea
to 413eb3f
Compare Pinging @elastic/es-distributed (Team:Distributed) |
* To be removed when REST compatibility with {@link org.elasticsearch.Version#V_8_6_0} / {@link RestApiVersion#V_8} no longer needed | ||
*/ | ||
@UpdateForV9(owner = UpdateForV9.Owner.DISTRIBUTED_COORDINATION) // to remove from the v9 API only | ||
@UpdateForV10(owner = UpdateForV10.Owner.DISTRIBUTED_COORDINATION) // to remove entirely |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think this pr closes #88978, until this is removed in 10, is it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it does - at least from the users' perspective with this change we no longer return the cluster state as described in #88978. There's some tech debt left behind (because of the need to support the v8 API still) but that's tracked with the @UpdateForV10
annotation, we don't need to keep an issue open too.
Including the cluster state in responses to the `POST _cluster/state` API was deprecated in elastic#90399 (v8.6.0) requiring callers to pass `?metric=none` to avoid the deprecation warning. This commit adjusts the behaviour as promised in v9 so that this API never returns the cluster state, and deprecates the `?metric` parameter itself. Closes elastic#88978
Including the cluster state in responses to the `POST _cluster/state` API was deprecated in elastic#90399 (v8.6.0) requiring callers to pass `?metric=none` to avoid the deprecation warning. This commit adjusts the behaviour as promised in v9 so that this API never returns the cluster state, and deprecates the `?metric` parameter itself. Closes elastic#88978
@DaveCTurner is this PR relevant to the serverless changelog? [FYI this question is based on 9.0 breaking changes] |
No, the reroute API is internal, end-users cannot access it in serverless. |
Including the cluster state in responses to the
POST _cluster/state
API was deprecated in #90399 (v8.6.0) requiring callers to pass
?metric=none
to avoid the deprecation warning. This commit adjusts thebehaviour as promised in v9 so that this API never returns the cluster
state, and deprecates the
?metric
parameter itself.Closes #88978