Hey guys,
I noticed this constraint on agg names
Supports sorting on sub-aggs down the current hierarchy. This is supported as long as the aggregation in the specified order path are of a single-bucket type, where the last aggregation in the path points to either a single-bucket aggregation or a metrics one. If it's a single-bucket aggregation, the sort will be applied on the document count in the bucket (i.e. doc_count), and if it is a metrics type, the sort will be applied on the pointed out metric (in case of a single-metric aggregations, such as avg, the sort will be applied on the single metric value)
NOTE: this commit adds a constraint on what should be considered a valid aggregation name. Aggregations names must be alpha-numeric and may contain '-' and '_'.
Closes #5253
changed 24 files
with 1011 additions
and 172 deletions .
It's not mentioned in the guide or under breaking changes for 1.1.0
(instead the breaking change is buried in the issue, which is an
enhancement)
It seems to me the most convenient name for a terms agg is the field name
itself, which very often contains the now non permited character '.'
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com .
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/bfa4dce9-7e56-42b9-a4ab-702f456ce608%40googlegroups.com .
For more options, visit https://groups.google.com/d/optout .