-
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 indices query #21837
Remove indices query #21837
Conversation
Although we said that this query can be removed in 6.0 as it was deprecated with 5.0, this change breaks backwards compatibility on the network layer. @s1monw what is our plan on changes like this? Can we just state that a search using this query will not work anymore against a mixed version cluster? Or do we want to somehow try and build a bw comp layer around this? |
@javanna I think we can't support stuff that is added in that fashion either. I think if you want to use 6 you have to stop using deprecated features before you do so. |
sounds good @s1monw thanks. |
@elasticmachine retest this please |
@jpountz would you mind reviewing this? |
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.
LGTM
@@ -10,6 +10,7 @@ | |||
only the strings `"true"` and `"false"` will be parsed into their boolean | |||
counterparts. Other strings will cause an error to be thrown. | |||
|
|||
* The deprecated indices query has been removed. |
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.
s/indices/indices
/?
28eff56
to
b72c15f
Compare
The indices query is deprecated since 5.0.0 (elastic#17710). It can now be removed in master (future 6.0 version).
b72c15f
to
52cca3f
Compare
The indices query is deprecated since 5.0.0 (#17710). It can now be removed in master (future 6.0 version).