Skip to content

make identificaiton of closed indices more clear #25253

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.

Sign up for GitHub

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

Closed
wants to merge 3 commits into from
Closed

make identificaiton of closed indices more clear #25253

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0e626e6
make identificaiton of closed indices more clear
Jun 9, 2017
8037d60
docs of closed indices about visibility and error
Jul 3, 2017
0018532
Update open-close.asciidoc
Aug 7, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/reference/indices/open-close.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,3 +32,10 @@ This setting can also be changed via the cluster update settings api.

Closed indices consume a significant amount of disk-space which can cause problems in managed environments. Closing indices can be disabled via the cluster settings
API by setting `cluster.indices.close.enable` to `false`. The default is `true`.

Most APIs, including _stats and _search, return `index_closed_exception` and 403 status code when accessing closed index. The `ignore_unavailable` querystring parameter allows to control whether closed index cause an error to be returned or not. Call to index `_aliases` returns correct value without error.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

403 recently became 400 . Can you update that?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when accessing closed indices

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whether closed indices cause an error to be returned or are skipped.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find this sentence confusing: "Call to index _aliases returns correct value without error. " I would remove it.


Closed indices are not returned in most wildcard API calls, like `_aliases`, `_stats` or `_search`, nor throw any exceptions. Closed indices behave like non-existent, closed indices will not be returned during call to `_aliases`. Passing `ignore_unavailable` is irrelevant to wildcard indices calls.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

expand_wildcards allows to control whether to expand wildcards against open, closed or both. can you update this sentence please?