-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
IndicesOptions wilcard state parsing is too lenient #50762
Labels
:Data Management/Indices APIs
APIs to create and manage indices and templates
Team:Data Management
Meta label for data/management team
Comments
jaymode
added
:Data Management/Indices APIs
APIs to create and manage indices and templates
team-discuss
labels
Jan 8, 2020
Pinging @elastic/es-core-features (:Core/Features/Indices APIs) |
+1 to remove the none with other leniency as is described in this issue. |
38 tasks
This has been open for quite a while, and we haven't made much progress on this due to focus in other areas. For now I'm going to close this as something we aren't planning on implementing. We can re-open it later if needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/Indices APIs
APIs to create and manage indices and templates
Team:Data Management
Meta label for data/management team
The logic to parse
IndicesOptions.WildcardStates
from a String or List of strings is overly lenient in that the ordering of values results in a different output whennone
is used as one of the values.The parsing should be made more strict to disallow none with other values. There could be some users relying on this behavior, so to maintain BWC we could deprecate the use of
none
with other values in 7.x and disallownone
with other values in 8.0.The text was updated successfully, but these errors were encountered: