-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Adding a deprecation info api check for custom types in templates #80676
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
Merged
masseyke
merged 4 commits into
elastic:7.16
from
masseyke:feature/deprecation-info-cutom-type-in-template
Nov 16, 2021
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
688abdf
Adding a deprecation info api check for custom types in templates
masseyke 70e2aff
combining logic for multiple types and custom types into one method
masseyke d47707f
spotlessApply, plus code simplification
masseyke e6f503f
minor fix
masseyke File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -37,6 +37,7 @@ | |
import java.util.Map; | ||
import java.util.Objects; | ||
import java.util.Set; | ||
import java.util.TreeSet; | ||
import java.util.concurrent.atomic.AtomicInteger; | ||
import java.util.stream.Collectors; | ||
import java.util.stream.StreamSupport; | ||
|
@@ -234,6 +235,34 @@ static DeprecationIssue checkTemplatesWithMultipleTypes(ClusterState state) { | |
); | ||
} | ||
|
||
static DeprecationIssue checkTemplatesWithCustomTypes(ClusterState state) { | ||
Set<String> templatesWithCustomTypes = new TreeSet<>(); | ||
state.getMetadata().getTemplates().forEach((templateCursor) -> { | ||
String templateName = templateCursor.key; | ||
ImmutableOpenMap<String, CompressedXContent> mappings = templateCursor.value.mappings(); | ||
if (mappings != null && mappings.size() == 1) { | ||
String typeName = mappings.iterator().next().key; | ||
if ("_doc".equals(typeName) == false) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Tiny comment, this could be There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oops, I'd meant to go back and find that constant! |
||
templatesWithCustomTypes.add(templateName); | ||
} | ||
} | ||
}); | ||
if (templatesWithCustomTypes.isEmpty()) { | ||
return null; | ||
} | ||
|
||
return new DeprecationIssue( | ||
DeprecationIssue.Level.CRITICAL, | ||
"Custom mapping types in index templates are deprecated", | ||
"https://ela.st/es-deprecation-7-custom-types", | ||
"Update or remove the following index templates before upgrading to 8.0: " | ||
+ templatesWithCustomTypes | ||
+ ". See https://ela.st/es-deprecation-7-removal-of-types for alternatives to mapping types.", | ||
false, | ||
null | ||
); | ||
} | ||
|
||
static DeprecationIssue checkClusterRoutingAllocationIncludeRelocationsSetting(final ClusterState clusterState) { | ||
return checkRemovedSetting( | ||
clusterState.metadata().settings(), | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think we should check the type name even if there is more than one mapping type. For example, a user could have both a
_default_
mapping and a custom one likesome_type
.This makes me think -- maybe this check could be combined with the one above
checkTemplatesWithMultipleTypes
? That way we could report all errors at once (both that they are using a_default_
mapping, and that they have an custom type name). The error message about "multiple types" could be improved to talk about a_default_
mapping to be more specific.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.
I was only checking for single mapping types with the thought that checkTemplatesWithMultipleTypes would catch the others. I'll see if I can find a clean way to combine them.
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.
My earlier comment was based on a misunderstanding -- I thought you couldn't have templates with multiple custom types in 7.x, but you actually can if they are carried over from 6.x! See #72540 for details. I thought this was only possible when using the
_default_
mapping, but that is not true. So no need to add special handling for_default_
.