Elasticsearch is introducing v2 of index templates. To understand the motivation for this change and it's details, see: elastic/elasticsearch#53101.
We need to ensure that when Beats creates index templates in a v2 index templates universe, the templates continue to work as before. If not, we need to figure out a migration path from v1 to v2 templates.
My strong suspicion is that the v1 index templates created by Beats should continue to function as-is as v2 index templates. This is mainly because the index pattern in a Beat's index template contain the Beat version, e.g. metricbeat-8.0.0-* or filebeat-7.5.3-*. So template inheritance doesn't come into play. And without template inheritance, there is not difference between v1 and v2 templates.
However, we still should confirm the above by testing against an actual ES cluster that has v2 templates implemented. That's what this issue is tracking.
Related: #17809
Elasticsearch is introducing v2 of index templates. To understand the motivation for this change and it's details, see: elastic/elasticsearch#53101.
We need to ensure that when Beats creates index templates in a v2 index templates universe, the templates continue to work as before. If not, we need to figure out a migration path from v1 to v2 templates.
My strong suspicion is that the v1 index templates created by Beats should continue to function as-is as v2 index templates. This is mainly because the index pattern in a Beat's index template contain the Beat version, e.g.
metricbeat-8.0.0-*orfilebeat-7.5.3-*.So template inheritance doesn't come into play. And without template inheritance, there is not difference between v1 and v2 templates.However, we still should confirm the above by testing against an actual ES cluster that has v2 templates implemented. That's what this issue is tracking.
Related: #17809