examples

Author: georgewallace

docs/reference/data-analysis/aggregations/search-aggregations-bucket-composite-aggregation.md

@@ -18,6 +18,64 @@ Unlike the other `multi-bucket` aggregations, you can use the `composite` aggreg
 
 The composite buckets are built from the combinations of the values extracted/created for each document and each combination is considered as a composite bucket.
 
+% 
+% [source,console]
+% --------------------------------------------------
+% PUT /sales
+% {
+%   "mappings": {
+%     "properties": {
+%       "product": {
+%           "type": "keyword"
+%       },
+%       "timestamp": {
+%           "type": "date"
+%       },
+%       "price": {
+%           "type": "long"
+%       },
+%       "shop": {
+%           "type": "keyword"
+%       },
+%       "location": {
+%           "type": "geo_point"
+%       },
+%       "nested": {
+%           "type": "nested",
+%           "properties": {
+%             "product": {
+%                 "type": "keyword"
+%             },
+%             "timestamp": {
+%                 "type": "date"
+%             },
+%             "price": {
+%                 "type": "long"
+%             },
+%             "shop": {
+%                 "type": "keyword"
+%             }
+%           }
+%        }
+%     }
+%   }
+% }
+% 
+% POST /sales/_bulk?refresh
+% {"index":{"_id":0}}
+% {"product": "mad max", "price": "20", "timestamp": "2017-05-09T14:35"}
+% {"index":{"_id":1}}
+% {"product": "mad max", "price": "25", "timestamp": "2017-05-09T12:35"}
+% {"index":{"_id":2}}
+% {"product": "rocky", "price": "10", "timestamp": "2017-05-08T09:10"}
+% {"index":{"_id":3}}
+% {"product": "mad max", "price": "27", "timestamp": "2017-05-10T07:07"}
+% {"index":{"_id":4}}
+% {"product": "apocalypse now", "price": "10", "timestamp": "2017-05-11T08:35"}
+% -------------------------------------------------
+% // TESTSETUP
+% 
+
 For example, consider the following document:
 
 ```js
@@ -27,6 +85,8 @@ For example, consider the following document:
 }
 ```
 
+%  NOTCONSOLE
+
 Using `keyword` and `number` as source fields for the aggregation results in the following composite buckets:
 
 ```js
@@ -38,6 +98,8 @@ Using `keyword` and `number` as source fields for the aggregation results in the
 { "keyword": "bar", "number": 76 }
 ```
 
+%  NOTCONSOLE
+
 ## Value sources [_value_sources]
 
 The `sources` parameter defines the source fields to use when building composite buckets. The order that the `sources` are defined controls the order that the keys are returned.
@@ -111,6 +173,32 @@ GET /_search
 }
 ```
 
+% [source,console-result]
+% ----
+% {
+%   "timed_out": false,
+%   "took": "$body.took",
+%   "_shards": {
+%     "total": 1,
+%     "successful": 1,
+%     "failed": 0,
+%     "skipped": 0
+%   },
+%   "hits": "$body.hits",
+%   "aggregations": {
+%     "my_buckets": {
+%       "after_key": { "dow": "Wednesday" },
+%       "buckets": [
+%         { "key": { "dow": "Monday"    }, "doc_count": 1 },
+%         { "key": { "dow": "Thursday"  }, "doc_count": 1 },
+%         { "key": { "dow": "Tuesday"   }, "doc_count": 2 },
+%         { "key": { "dow": "Wednesday" }, "doc_count": 1 }
+%       ]
+%     }
+%   }
+% }
+% ----
+
 Although similar, the `terms` value source doesn’t support the same set of parameters as the `terms` aggregation. For other supported value source parameters, see:
 
 * [Order](#_order)
@@ -180,6 +268,31 @@ GET /_search
 }
 ```
 
+% [source,console-result]
+% ----
+% {
+%   "timed_out": false,
+%   "took": "$body.took",
+%   "_shards": {
+%     "total": 1,
+%     "successful": 1,
+%     "failed": 0,
+%     "skipped": 0
+%   },
+%   "hits": "$body.hits",
+%   "aggregations": {
+%     "my_buckets": {
+%       "after_key": { "price": 20.0 },
+%       "buckets": [
+%         { "key": { "price": 10.0 }, "doc_count": 2 },
+%         { "key": { "price": 15.0 }, "doc_count": 1 },
+%         { "key": { "price": 20.0 }, "doc_count": 2 }
+%       ]
+%     }
+%   }
+% }
+% ----
+
 
 ### Date histogram [_date_histogram]
 
@@ -311,6 +424,8 @@ Instead of a single bucket starting at midnight, the above request groups the do
 }
 ```
 
+%  TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
+
 ::::{note}
 The start `offset` of each bucket is calculated after `time_zone` adjustments have been made.
 ::::
@@ -514,6 +629,8 @@ GET /_search
 }
 ```
 
+%  TEST[s/_search/_search\?filter_path=aggregations/]
+
 ... returns:
 
 ```console-result
@@ -546,6 +663,8 @@ GET /_search
 }
 ```
 
+%  TESTRESPONSE[s/\.\.\.//]
+
 To get the next set of buckets, resend the same aggregation with the `after` parameter set to the `after_key` value returned in the response. For example, this request uses the `after_key` value provided in the previous response:
 
 $$$composite-aggregation-after-example$$$
@@ -710,6 +829,8 @@ GET /_search
 }
 ```
 
+%  TEST[s/_search/_search\?filter_path=aggregations/]
+
 ... returns:
 
 ```console-result
@@ -768,6 +889,8 @@ GET /_search
 }
 ```
 
+%  TESTRESPONSE[s/\.\.\.//]
+
 
 ## Pipeline aggregations [search-aggregations-bucket-composite-aggregation-pipeline-aggregations]
 

docs/reference/data-analysis/aggregations/search-aggregations-metrics-avg-aggregation.md

@@ -20,6 +20,8 @@ POST /exams/_search?size=0
 }
 ```
 
+%  TEST[setup:exams]
+
 The above aggregation computes the average grade over all documents. The aggregation type is `avg` and the `field` setting defines the numeric field of the documents the average will be computed on. The above will return the following:
 
 ```console-result
@@ -33,6 +35,8 @@ The above aggregation computes the average grade over all documents. The aggrega
 }
 ```
 
+%  TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
+
 The name of the aggregation (`avg_grade` above) also serves as the key by which the aggregation result can be retrieved from the returned response.
 
 ## Script [_script_2]
@@ -63,6 +67,21 @@ POST /exams/_search?size=0
 }
 ```
 
+%  TEST[setup:exams]
+
+%  TEST[s/size=0/size=0&filter_path=aggregations/]
+
+% [source,console-result]
+% ----
+% {
+%   "aggregations": {
+%     "avg_corrected_grade": {
+%       "value": 80.0
+%     }
+%   }
+% }
+% ----
+
 
 ## Missing value [_missing_value_6]
 
@@ -82,6 +101,8 @@ POST /exams/_search?size=0
 }
 ```
 
+%  TEST[setup:exams]
+
 1. Documents without a value in the `grade` field will fall into the same bucket as documents that have the value `10`.
 
 
@@ -134,4 +155,6 @@ For each histogram field the `avg` aggregation adds each number in the `values`
 }
 ```
 
+%  TESTRESPONSE[skip:test not setup]
+