-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Move internal index templates to composable templates #61457
Move internal index templates to composable templates #61457
Conversation
@elasticmachine run elasticsearch-ci/bwc |
@elasticmachine update branch |
Pinging @elastic/es-core-features (:Core/Features/ILM+SLM) |
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 but you shouldn't take my word for 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.
Thanks for working on this @probakowski, I left some comments about missing _meta
maps in some of the templates (we need these to indicate in the UI that a template is managed by ES automatically).
I was thinking though, that we should increment the version to indicate the change, that way a user is not left with a version: 2
legacy template and version: 2
composable index template; they can immediately tell from the version: 3
signifier that the composable index template version is "newer" (since the old one will not be removed) even if they are not familiar with the difference between the types of templates.
@dakrone that makes sense, I've increased version in all templates |
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, but there is one more missing version increment, in ILMHistoryTemplateRegistry
we need to increment the version for the ilm history index template
Good catch, I've updated it as well, thanks! |
...plugin/ilm/src/main/java/org/elasticsearch/xpack/ilm/history/ILMHistoryTemplateRegistry.java
Outdated
Show resolved
Hide resolved
…story/ILMHistoryTemplateRegistry.java Co-authored-by: Lee Hinman <[email protected]>
pinging @elastic/es-ui, FYI this change updates version field in |
This change moves watcher, ILM history and SLM history templates to composable templates. Versions are updated to reflect the switch. Only change to the templates themselves is added `_meta` to mark them as managed
Thank you for the ping @probakowski! To help me understand what needs to change in the UI, could you please describe how the watcher, SLM, and ILM APIs have changed? |
Possilby after #61457, the priority we use for the index template that converts core yaml tests to use runtime fields is already taken, which causes an error as there ma be multiple matching templates with same priority.
@cjcenizal I don't know if you consider this API but versions templates and some internal indices got upgraded:
According to note in WatcherIndexTemplateRegistryField UI should be notified when these version changes as UI needs to be updated |
This change fixed settings accidentally changed in elastic#61457, this fixes ability of ILM history index to rollover. It also adds test to make sure we can't hit this kind of bug in the future. Closes elastic#61863
…61661) This change moves watcher, ILM history and SLM history templates to composable templates. Versions are updated to reflect the switch. Only change to the templates themselves is added `_meta` to mark them as managed
This change moves watcher, ILM history and SLM history templates to composable templates.
Versions are updated to reflect the switch. Only change to the templates themselves is added
_meta
to mark them as managed