Replace ignore_indices with ignore_unavailable, expand_wildcards and allow_no_indices
#4453
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…` and `allow_no_indices`. * `ignore_unavailable` - Controls whether to ignore if any specified indices are unavailable, this includes indices that don't exist or closed indices. Either `true` or `false` can be specified. * `allow_no_indices` - Controls whether to fail if a wildcard indices expressions results into no concrete indices. Either `true` or `false` can be specified. For example if the wildcard expression `foo*` is specified and no indices are available that start with `foo` then depending on this setting the request will fail. This setting is also applicable when `_all`, `*` or no index has been specified. * `expand_wildcards` - Controls to what kind of concrete indices wildcard indices expression expand to. If `open` is specified then the wildcard expression if expanded to only open indices and if `closed` is specified then the wildcard expression if expanded only to closed indices. Also both values (`open,closed`) can be specified to expand to all indices. Relates to elastic#4436
ghost
assigned 
|
Re
|
|
pushed to master |
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this pull request
Jan 12, 2014
…Index Settings" APIs * prefix * ignore_indices * ignore_unavailable * allow_no_indices * expand_wildcards * flat_settings Related: elastic/elasticsearch#4436, elastic/elasticsearch#4453
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this pull request
Mar 13, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ignore_unavailable- Controls whether to ignore if any specified indices are unavailable, this includes indicesthat don't exist or closed indices. Either
trueorfalsecan be specified.allow_no_indices- Controls whether to fail if a wildcard indices expressions results into no concrete indices.Either
trueorfalsecan be specified. For example if the wildcard expressionfoo*is specified and no indicesare available that start with
foothen depending on this setting the request will fail. This setting is also applicablewhen
_all,*or no index has been specified.expand_wildcards- Controls to what kind of concrete indices wildcard indices expression expand to. Ifopenisspecified then the wildcard expression if expanded to only open indices and if
closedis specified then the wildcard expression if expanded only to closed indices. Also both values (open,closed) can be specified to expand to all indices.There're a number of apis that support multiple indices, but didn't support the
ignore_indicesoption. I haven't cut these apis over to the new indices options. I'll do that after this PR gets in. The following apis don't support for the new indices options yet: mlt, delete index, delete mapping, delete warmer, index exists, get indices settings, put index settings, put mappings and put warmer apisRelates to #4436