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
The composable index templates are introduced in Elasticsearch 7.8. The plan was to deprecate the legacy template API in Elasticsearch 8.0, but as of now, the deprecation defers to 9.0.
It is valid to use both APIs in ES 8.x. Currently, the plugin uses legacy API for ES 7.x and forces to use index template API for ES 8.x. This issue is to request backward compatibility for users to choose which API to use.
One suggestion is to provide a boolean flag template_legacy => auto/true/false (default auto) to use legacy API
The text was updated successfully, but these errors were encountered:
This commit adds a new flag template_api to control which API to use. The available value is auto, legacy and composable. The default value is auto.
Fixed: #1088
Co-authored-by: Ry Biesemeyer <[email protected]>
The composable index templates are introduced in Elasticsearch 7.8. The plan was to deprecate the legacy template API in Elasticsearch 8.0, but as of now, the deprecation defers to 9.0.
It is valid to use both APIs in ES 8.x. Currently, the plugin uses legacy API for ES 7.x and forces to use index template API for ES 8.x. This issue is to request backward compatibility for users to choose which API to use.
One suggestion is to provide a boolean flag
template_legacy
=> auto/true/false (default auto) to use legacy APIThe text was updated successfully, but these errors were encountered: