-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[ILM] Delete min_age field if warm phase on rollover is enabled #45412
[ILM] Delete min_age field if warm phase on rollover is enabled #45412
Conversation
Pinging @elastic/es-ui |
FYI @bmcconaghy |
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.
Code LGTM.
💚 Build Succeeded |
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.
Code LGTM, didn't test locally.
delete esPhase.min_age; | ||
} | ||
|
||
{esPhase.actions = esPhase.actions || {};} |
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.
Sorry, actually, I just noticed this. Why is this wrapped in braces?
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.
Strange! That was not intentional. Thanks for catching this! I removed it and did some quick manual testing again to verify everything is still working as expected.
💚 Build Succeeded |
This PR fixes a bug in ILM where a user was not able to successfully enable
Move to warm phase on rollover
in edit mode after previously having this disabled.Fixes #39328
Testing
Steps to reproduce are outlined in the issue. You will need to specify node attributes when you start up ES.
Release notes
Previously, a user was unable to successfully enable the
Move to warm phase on rollover
setting when editing an index lifecycle policy that previously had this setting disabled. This change fixes the issue.