-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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 support for wait_for_active_shards=index-setting in index close API #114709
Remove support for wait_for_active_shards=index-setting in index close API #114709
Conversation
…e API Specifiying `wait_for_active_shards=index-setting` was deprecared in elastic#67158 (8.0). It's redundant since it's the default behaviour in 8.x
Hi @arteam, I've created a changelog YAML for you. Note that since this PR is labelled |
// TODO in v9: | ||
// - throw an IllegalArgumentException here | ||
// - record the removal of support for this value as a breaking change | ||
throw new IllegalArgumentException("wait_for_active_shards=index-setting shouldn't be used"); |
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.
We need to preserve the v8 behaviour here still if RestApiVersion.V_8
is specified.
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.
Yes, just saw a comment about that in the dev issue 👍
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.
👍 that applies to all other similar breaking changes too btw
…or-active-shards-index-settings
…or-active-shards-index-settings
…or-active-shards-index-settings
Hi @arteam, I've created a changelog YAML for you. Note that since this PR is labelled |
@elasticmachine update branch |
…or-active-shards-index-settings
…or-active-shards-index-settings
The issue is now owned by the Data Management team, see #115837. |
Specifiying
wait_for_active_shards=index-setting
was deprecared in #67158 (8.0). It's redundant since it's the default behaviour in 8.x