You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we upgrade Elasticsearch to 8.x and use legacy template (template_api=>legacy), the plugin resolves the composable style template as a default template and send to legacy API, obviously it doesn't work (see the produced error below).
The discussion with team brought to the idea of using legacy template api with custom template only. However, if ILM (ilm_* settings) is enabled, the plugin crashes. When plugin tries to set ILM settings to provided custom template, the plugin aligns on Elasticsearch version (pseudo: template_settings = version < 8 ? template['settings']: template['template']['settings']). Obviously, with custom flexible template it is hard to guess where ILM settings located.
Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
set template_api to legacy
connect to any (including cloud) Elasticsearch where its version is 8.x+
Issue description
When we upgrade Elasticsearch to 8.x and use legacy template (
template_api
=>legacy
), the plugin resolves the composable style template as a default template and send to legacy API, obviously it doesn't work (see the produced error below).The discussion with team brought to the idea of using legacy template api with custom template only. However, if ILM (ilm_* settings) is enabled, the plugin crashes. When plugin tries to set ILM settings to provided custom template, the plugin aligns on Elasticsearch version (pseudo:
template_settings = version < 8 ? template['settings']: template['template']['settings']
). Obviously, with custom flexible template it is hard to guess where ILM settings located.Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
template_api
tolegacy
Provide logs (if relevant):
Acceptance Criteria
The text was updated successfully, but these errors were encountered: