-
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
Docs: ILM document behaviour for changing lifecycle setting #75790
Docs: ILM document behaviour for changing lifecycle setting #75790
Conversation
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-core-features (Team:Core/Features) |
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.
Thanks @andreidan. The changes look good but may be redundant. WDYT?
The name of the policy to use to manage the index. As the current executing phase | ||
definition is cached in the index metadata, changing the setting to a different policy | ||
will not affect the currently executing phase, but the next phase will be read from | ||
the newly configured policy. |
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.
This seems to say the same thing as https://www.elastic.co/guide/en/elasticsearch/reference/master/update-lifecycle-policy.html#ilm-apply-new-policy. I wonder if we should just add an xref to there?
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.
@jrodewig great point! I missed that we document this already. An xref sounds great
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.
Awesome. I pushed 28f7fce to add an xref.
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. Thanks @andreidan.
…75790) Add xref Co-authored-by: James Rodewig <[email protected]>
💚 Backport successful
|
…75827) Add xref Co-authored-by: James Rodewig <[email protected]> Co-authored-by: Andrei Dan <[email protected]> Co-authored-by: James Rodewig <[email protected]>
…75790) Add xref Co-authored-by: James Rodewig <[email protected]>
Closes #70151