-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Made small modifications to ESRestTestCase. #70531
Conversation
* Don't try to invoke delete component/index templates APIs if there are no templates to delete. * Don't delete deprecation templates by marking these as xpack templates. Relates to elastic#69973
Pinging @elastic/es-core-features (Team:Core/Features) |
@@ -1391,6 +1395,9 @@ protected static boolean isXPackTemplate(String name) { | |||
if (name.startsWith(".transform-")) { | |||
return true; | |||
} | |||
if (name.startsWith(".deprecation-")) { |
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 is for: .deprecation-indexing-mappings
, .deprecation-indexing-settings
and .deprecation-indexing-template
templates.
@@ -1391,6 +1395,9 @@ protected static boolean isXPackTemplate(String name) { | |||
if (name.startsWith(".transform-")) { | |||
return true; | |||
} | |||
if (name.startsWith(".deprecation-")) { |
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.
Referencing #66413 here, because all this logic in this class about protecting xpack related templates wouldn't be needed if these component and composable index templates are system owned.
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
If we're concerned about the speed of deleting the templates for older (pre 7.13) clusters, what about performing the deletes in parallel instead of waiting to delete them one-by-one serially? (maybe in a future PR)
Good idea, perhaps this could work. I will try this out. I do wonder how much this going to help for the slow build machines. |
Backporting elastic#70531 to the 7.x branch. * Don't try to invoke delete component/index templates APIs if there are no templates to delete. * Don't delete deprecation templates by marking these as xpack templates. Relates to elastic#69973
Backporting elastic#70531 to the 7.12 branch. * Don't try to invoke delete component/index templates APIs if there are no templates to delete. * Don't delete deprecation templates by marking these as xpack templates. Relates to elastic#69973
Backporting elastic#70531 to the 7.11 branch. * Don't try to invoke delete component/index templates APIs if there are no templates to delete. * Don't delete deprecation templates by marking these as xpack templates. Relates to elastic#69973
Relates to #69973