Skip to content

Commit d6a3241

Browse files
georgewallacegeorgewallace
authored
Apply suggestions from code review
1 parent 3fd8356 commit d6a3241

6 files changed

+0
-41
lines changed

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

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,6 @@ Response:
6464
}
6565
}
6666
```
67-
6867
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
6968

7069
::::{warning}
@@ -102,7 +101,6 @@ POST /sales/_search?size=0
102101
}
103102
}
104103
```
105-
106104
% TEST[setup:sales]
107105

108106
1. Documents without a value in the `date` field will be added to the "Older" bucket, as if they had a date value of "1976-11-30".
@@ -227,7 +225,6 @@ POST /sales/_search?size=0
227225
}
228226
}
229227
```
230-
231228
% TEST[setup:sales]
232229

233230
1. This date will be converted to `2016-02-01T00:00:00.000+01:00`.
@@ -259,7 +256,6 @@ POST /sales/_search?size=0
259256
}
260257
}
261258
```
262-
263259
% TEST[setup:sales s/now-10M\/M/10-2015/]
264260

265261
Response:
@@ -285,7 +281,6 @@ Response:
285281
}
286282
}
287283
```
288-
289284
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
290285

291286
It is also possible to customize the key for each range:
@@ -310,7 +305,6 @@ POST /sales/_search?size=0
310305
}
311306
}
312307
```
313-
314308
% TEST[setup:sales]
315309

316310
Response:
@@ -340,7 +334,6 @@ Response:
340334
}
341335
}
342336
```
343-
344337
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
345338

346339

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

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,6 @@ Response:
8484
}
8585
}
8686
```
87-
8887
% TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
8988

9089

@@ -119,7 +118,6 @@ POST /museums/_search?size=0
119118
}
120119
}
121120
```
122-
123121
% TEST[continued]
124122

125123
Response:
@@ -150,7 +148,6 @@ Response:
150148
}
151149
}
152150
```
153-
154151
% TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
155152

156153

@@ -177,7 +174,6 @@ POST /museums/_search?size=0
177174
}
178175
}
179176
```
180-
181177
% TEST[continued]
182178

183179
Response:
@@ -205,7 +201,6 @@ Response:
205201
}
206202
}
207203
```
208-
209204
% TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
210205

211206

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

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,6 @@ POST /sales/_search?size=0
3535
}
3636
}
3737
```
38-
3938
% TEST[setup:sales]
4039

4140
1. The `global` aggregation has an empty body
@@ -62,7 +61,6 @@ The response for the above aggregation:
6261
}
6362
}
6463
```
65-
6664
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
6765

6866
1. The number of documents that were aggregated (in our case, all documents within the search context)

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

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,6 @@ POST /network-traffic/_bulk?refresh
4444
{"index":{"_id":8}}
4545
{"ipv4":"192.168.3.107","ipv6":"2001:db8:a4f8:114f:6001:0:12:7307"}
4646
```
47-
4847
% TESTSETUP
4948

5049
The following aggregation groups documents into buckets. Each bucket identifies a different sub-network. The sub-network is calculated by applying a netmask with prefix length of `24` to each IP address in the `ipv4` field:
@@ -65,7 +64,6 @@ GET /network-traffic/_search
6564
}
6665
}
6766
```
68-
6967
% TEST
7068

7169
Response:
@@ -103,7 +101,6 @@ Response:
103101
}
104102
}
105103
```
106-
107104
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
108105

109106
To aggregate IPv6 addresses, set `is_ipv6` to `true`.
@@ -125,7 +122,6 @@ GET /network-traffic/_search
125122
}
126123
}
127124
```
128-
129125
% TEST
130126

131127
If `is_ipv6` is `true`, the response doesn’t include a `netmask` for each bucket.
@@ -160,7 +156,6 @@ If `is_ipv6` is `true`, the response doesn’t include a `netmask` for each buck
160156
}
161157
}
162158
```
163-
164159
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
165160

166161

@@ -226,7 +221,6 @@ GET /network-traffic/_search
226221
}
227222
}
228223
```
229-
230224
% TEST
231225

232226
Response:
@@ -261,7 +255,6 @@ Response:
261255
}
262256
}
263257
```
264-
265258
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
266259

267260

@@ -288,7 +281,6 @@ GET /network-traffic/_search
288281
}
289282
}
290283
```
291-
292284
% TEST
293285

294286
Response:
@@ -326,7 +318,6 @@ Response:
326318
}
327319
}
328320
```
329-
330321
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
331322

332323

@@ -351,7 +342,6 @@ GET /network-traffic/_search
351342
}
352343
}
353344
```
354-
355345
% TEST
356346

357347
Response:
@@ -382,7 +372,6 @@ Response:
382372
}
383373
}
384374
```
385-
386375
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
387376

388377

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

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,6 @@ GET /ip_addresses/_search
3030
}
3131
}
3232
```
33-
3433
% TEST[setup:iprange]
3534

3635
Response:
@@ -57,7 +56,6 @@ Response:
5756
}
5857
}
5958
```
60-
6159
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
6260

6361
IP ranges can also be defined as CIDR masks:
@@ -81,7 +79,6 @@ GET /ip_addresses/_search
8179
}
8280
}
8381
```
84-
8582
% TEST[setup:iprange]
8683

8784
Response:
@@ -110,7 +107,6 @@ Response:
110107
}
111108
}
112109
```
113-
114110
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
115111

116112
## Keyed Response [_keyed_response_3]
@@ -137,7 +133,6 @@ GET /ip_addresses/_search
137133
}
138134
}
139135
```
140-
141136
% TEST[setup:iprange]
142137

143138
Response:
@@ -162,7 +157,6 @@ Response:
162157
}
163158
}
164159
```
165-
166160
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
167161

168162
It is also possible to customize the key for each range:
@@ -187,7 +181,6 @@ GET /ip_addresses/_search
187181
}
188182
}
189183
```
190-
191184
% TEST[setup:iprange]
192185

193186
Response:
@@ -212,7 +205,6 @@ Response:
212205
}
213206
}
214207
```
215-
216208
% TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
217209

218210

‎docs/reference/data-analysis/aggregations/search-aggregations-bucket-multi-terms-aggregation.md‎

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,6 @@ GET /products/_search
7070
}
7171
}
7272
```
73-
7473
% TEST[s/_search/_search\?filter_path=aggregations/]
7574

7675
1. `multi_terms` aggregation can work with the same field types as a [`terms aggregation`](/reference/data-analysis/aggregations/search-aggregations-bucket-terms-aggregation.md#search-aggregations-bucket-terms-aggregation-order) and supports most of the terms aggregation parameters.
@@ -123,7 +122,6 @@ Response:
123122
}
124123
}
125124
```
126-
127125
% TESTRESPONSE[s/\.\.\.//]
128126

129127
1. an upper bound of the error on the document counts for each term, see <<search-aggregations-bucket-multi-terms-aggregation-approximate-counts,below>
@@ -191,7 +189,6 @@ GET /products/_search
191189
}
192190
}
193191
```
194-
195192
% TEST[s/_search/_search\?filter_path=aggregations/]
196193

197194
Response:
@@ -233,7 +230,6 @@ Response:
233230
}
234231
}
235232
```
236-
237233
% TESTRESPONSE[s/\.\.\.//]
238234

239235

@@ -263,7 +259,6 @@ GET /products/_search
263259
}
264260
}
265261
```
266-
267262
% TEST[s/_search/_search\?filter_path=aggregations/]
268263

269264
Response:
@@ -321,7 +316,6 @@ Response:
321316
}
322317
}
323318
```
324-
325319
% TESTRESPONSE[s/\.\.\.//]
326320

327321
1. Documents without a value in the `product` field will fall into the same bucket as documents that have the value `Product Z`.
@@ -371,7 +365,6 @@ GET /products/_search
371365
}
372366
}
373367
```
374-
375368
% TEST[s/_search/_search\?filter_path=aggregations/]
376369

377370
```console-result
@@ -431,7 +424,6 @@ GET /products/_search
431424
}
432425
}
433426
```
434-
435427
% TESTRESPONSE[s/\.\.\.//]
436428

437429

0 commit comments

Comments
 (0)