Skip to content
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

request of using legacy template API in Elasticsearch 8.x #1088

Closed
kaisecheng opened this issue Sep 29, 2022 · 0 comments · Fixed by #1092
Closed

request of using legacy template API in Elasticsearch 8.x #1088

kaisecheng opened this issue Sep 29, 2022 · 0 comments · Fixed by #1092
Assignees

Comments

@kaisecheng
Copy link
Contributor

kaisecheng commented Sep 29, 2022

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

kaisecheng added a commit that referenced this issue Oct 12, 2022
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants