WARNING: Version 6.0 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Aggregations changes
editAggregations changes
editDeprecated pattern element of include/exclude for terms aggregations has been removed
editThe include and exclude options of terms aggregations used to accept a
sub pattern object which has been removed. The pattern should now be directly
put as a value of the include and exclude fields. For instance, the below
terms aggregation:
POST /twitter/_search?size=0
{
"aggs" : {
"top_users" : {
"terms" : {
"field" : "user",
"include": {
"pattern": "foo.*"
},
"exclude": {
"pattern": ".*bar"
}
}
}
}
}
should be replaced with:
POST /twitter/_search?size=0
{
"aggs" : {
"top_users" : {
"terms" : {
"field" : "user",
"include": "foo.*",
"exclude": ".*bar"
}
}
}
}
Numeric to and from parameters in date_range aggregation are interpreted according to format now
editNumeric to and from parameters in date_range aggregations used to always be interpreted as epoch_millis,
making other numeric formats like epoch_seconds unusable for numeric input values.
Now we interpret these parameters according to the format of the target field.
If the format in the mappings is not compatible with the numeric input value, a compatible
format (e.g. epoch_millis, epoch_second) must be specified in the date_range aggregation, otherwise an error is thrown.