-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Document _cat/indices behavior when encountering source only indices #114884
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
Document _cat/indices behavior when encountering source only indices #114884
Conversation
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-distributed (Team:Distributed) |
docs/reference/cat/indices.asciidoc
Outdated
<<search-count,count>> APIs. | ||
|
||
Note that information such as document count, deleted document count and store size are not shown for | ||
<<snapshots-source-only-repository, source-only indices>> since these indices do not contain the relevant |
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.
The term source-only indices
is not used elsewhere and may be confusing. Could we call them "indices restored from a source-only snapshot" instead just to avoid any ambiguity?
level `meta` element. | ||
Note that information such as document count, deleted document count and store size are not available for | ||
source-only indices since these indices do not contain the relevant data structures to retrieve this information from. |
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.
Similarly here re. the phrase source-only indices
. Also could this just be another bullet point in the list of constraints on indices restored from source-only snapshots?
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
💔 Backport failedThe backport operation could not be completed due to the following error:
You can use sqren/backport to manually backport by running |
Closes #114546