-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Error when updating component template when index template has "index.mode=time_series"
#91592
Labels
>bug
:Data Management/Data streams
Data streams and their lifecycles
:StorageEngine/TSDB
You know, for Metrics
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Team:Data Management
Meta label for data/management team
Comments
elasticsearchmachine
added
the
needs:triage
Requires assignment of a team area label
label
Nov 15, 2022
For reference: Index template:
Component template with dimension field:
|
elasticsearchmachine
removed
the
Team:Data Management
Meta label for data/management team
label
Nov 15, 2022
6 tasks
martijnvg
added
>bug
:Data Management/Data streams
Data streams and their lifecycles
:StorageEngine/TSDB
You know, for Metrics
and removed
needs:triage
Requires assignment of a team area label
labels
Nov 15, 2022
elasticsearchmachine
added
Team:Data Management
Meta label for data/management team
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
labels
Nov 15, 2022
Pinging @elastic/es-analytics-geo (Team:Analytics) |
Pinging @elastic/es-data-management (Team:Data Management) |
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Nov 16, 2022
If index templates make use of the auto index.routing_path generation and use component templates then making any chang to component templates will fail. This commit addresses this, by changing the logic that creates/updates component templates to use the index settings provider when validating index templates that use the component templates being updated. Closes elastic#91592
elasticsearchmachine
pushed a commit
that referenced
this issue
Nov 22, 2022
…91615) If index templates make use of the auto index.routing_path generation and use component templates then making any chang to component templates will fail. This commit addresses this, by changing the logic that creates/updates component templates to use the index settings provider when validating index templates that use the component templates being updated. Closes #91592
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Nov 22, 2022
…lastic#91615) If index templates make use of the auto index.routing_path generation and use component templates then making any chang to component templates will fail. This commit addresses this, by changing the logic that creates/updates component templates to use the index settings provider when validating index templates that use the component templates being updated. Closes elastic#91592
elasticsearchmachine
pushed a commit
that referenced
this issue
Nov 22, 2022
…91615) (#91792) If index templates make use of the auto index.routing_path generation and use component templates then making any chang to component templates will fail. This commit addresses this, by changing the logic that creates/updates component templates to use the index settings provider when validating index templates that use the component templates being updated. Closes #91592
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Data Management/Data streams
Data streams and their lifecycles
:StorageEngine/TSDB
You know, for Metrics
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Team:Data Management
Meta label for data/management team
While working on a Fleet feature came across an issue:
In Fleet, added
index.mode=time_series
setting tometrics-system.cpu
Index Template, and relying on ES automation to fill therouting_path
field.This worked fine regards to generating the
routing_path
field in the data streams.However, when subsequently trying to update a parent
metrics-system.cpu@custom
Component Template, I ran into an issue saying that the resulting template is invalid, see error below.After discussing with @martijnvg on Slack, the conclusion was that this should be fixed in elasticsearch:
When the put component template api validates an index template that a component template it is updating is using, we should generate the routing path as well.
Also, the update should fail if there are no dimension fields in the mappings.
Error message:
Originally posted by @juliaElastic in #74660 (comment)
The text was updated successfully, but these errors were encountered: