-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Add a cluster deprecation check for index templates containing multiple types #72540
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
Add a cluster deprecation check for index templates containing multiple types #72540
Conversation
Pinging @elastic/es-search (Team:Search) |
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 for adding this deprecation @romseygeek! The deprecation message LGTM as well as implementation from a high level. I'll defer to an ES engineer if you'd like a more thorough code review.
Thanks @alisonelizabeth, I've pinged @jtibshirani to get an ES view on it. |
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.
Looks good to me!
if (templatesWithMultipleTypes.isEmpty()) { | ||
return null; | ||
} | ||
return new DeprecationIssue(DeprecationIssue.Level.CRITICAL, |
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.
Just for my knowledge, does CRITICAL
mean we'll prevent the upgrade from proceeding?
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.
Good question, I've asked in the core-features channel and will try to find out!
Using an index template that creates multiple mapping types will already
throw an error in 7.x. This upgrade check should help filter out any unused
templates with multiple types that are still lurking in the cluster state.