-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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 support for _meta field to ILM policies #70755
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>enhancement
Team:Data Management
Meta label for data/management team
Comments
Pinging @elastic/es-core-features (Team:Core/Features) |
@dakrone, can I work on the issue? I'm interested in ILM and have submitted several PRs for ILM. |
@gaobinlong certainly, that would be great, feel free to ping me if you need any assistance. |
dakrone
pushed a commit
that referenced
this issue
Jun 1, 2021
Relates to #70755. The main changes of this PR are: Add an optional _meta field to ILM policy. Add some test code about the change. Update the doc of Create or update lifecycle policy API.
dakrone
pushed a commit
to dakrone/elasticsearch
that referenced
this issue
Jun 1, 2021
Relates to elastic#70755. The main changes of this PR are: Add an optional _meta field to ILM policy. Add some test code about the change. Update the doc of Create or update lifecycle policy API.
This has been resolved in #73515, thanks again @gaobinlong |
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>enhancement
Team:Data Management
Meta label for data/management team
We support the
_meta
key as an object that can contain any data in our component and composable index templates. We use this functionality to be able to give these objects descriptions and indicate whether they are managed by Elasticsearch.We should add support for this
_meta
field to ILM policies themselves.The text was updated successfully, but these errors were encountered: