-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Closed
Labels
Feature:AggregationsAggregation infrastructure (AggConfig, esaggs, ...)Aggregation infrastructure (AggConfig, esaggs, ...)Feature:SearchQuerying infrastructure in KibanaQuerying infrastructure in KibanaenhancementNew value added to drive a business resultNew value added to drive a business resultimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:smallSmall Level of EffortSmall Level of Effort
Description
Kibana version: 6.5.1
Steps to reproduce:
- Define two pipeline aggregations as metrics on the same underlying bucketing aggregation
- Kibana will ask both aggs to be calculated
Expected behavior: Kibana should deduplicate the same underlying aggregation and only run them once.
Imagine asking for both avg and max buckets, underlying request then looks like:
{
"aggs": {
"1": {
"max_bucket": {
"buckets_path": "1-bucket>_count"
}
},
"2": {
"avg_bucket": {
"buckets_path": "2-bucket>_count"
}
},
"1-bucket": {
"date_histogram": {
"field": "Date",
"interval": "1M",
"time_zone": "Europe/Berlin",
"min_doc_count": 1
}
},
"2-bucket": {
"date_histogram": {
"field": "Date",
"interval": "1M",
"time_zone": "Europe/Berlin",
"min_doc_count": 1
}
}
},
"size": 0,
"_source": {
"excludes": []
},
"stored_fields": [
"*"
],
"script_fields": {},
"docvalue_fields": [
{
"field": "Date",
"format": "date_time"
}
],
"query": {
"bool": {
"must": [],
"filter": [
{
"match_all": {}
}
],
"should": [],
"must_not": []
}
}
}Metadata
Metadata
Assignees
Labels
Feature:AggregationsAggregation infrastructure (AggConfig, esaggs, ...)Aggregation infrastructure (AggConfig, esaggs, ...)Feature:SearchQuerying infrastructure in KibanaQuerying infrastructure in KibanaenhancementNew value added to drive a business resultNew value added to drive a business resultimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:smallSmall Level of EffortSmall Level of Effort
