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
{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "Failed to parse mapping: Field [time_series_dimension] requires that [index] and [doc_values] are true"
}
],
"type": "mapper_parsing_exception",
"reason": "Failed to parse mapping: Field [time_series_dimension] requires that [index] and [doc_values] are true",
"caused_by": {
"type": "illegal_argument_exception",
"reason": "Field [time_series_dimension] requires that [index] and [doc_values] are true"
}
},
"status": 400
}
@pxsalehi it'd be the data management team. But we take care of this within the OTel program and will ask them for review once there is a PR. That's why I assigned it to myself.
Thanks, I've tagged this for the data management team. We just need an area team label on the thing for administrative purposes, even if it's assigned to an individual.
Elasticsearch Version
main
Installed Plugins
otel-data
Java Version
bundled
OS Version
Problem Description
Part of the OTel effort.
No user impact, this is disabled by default.
That happens because some dynamic mappings with
match_mapping_type
setindex: false
- while those fields are set as dimension andindex: false
can't be set for dimensions.Ideas so far: we move back the new metrics added into https://github.com/elastic/elasticsearch/blob/73e7b737ac17db1bc0f57891674e0b5efdf3d484/x-pack/plugin/core/template-resources/src/main/resources/metrics%40mappings.json into the
otel-data
plugin and if anything left, we can duplicate those and then leaving out the ones that setindex: false
.Steps to Reproduce
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: