@@ -181,7 +181,7 @@ node.
181
181
182
182
[source,console]
183
183
----
184
- GET _cat/shards
184
+ GET _cat/shards?v=true
185
185
----
186
186
// TEST[setup:my_index]
187
187
@@ -201,7 +201,7 @@ configure `index.routing.allocation.total_shards_per_node` using the
201
201
202
202
[source,console]
203
203
--------------------------------------------------
204
- PUT / my-index-000001/_settings
204
+ PUT my-index-000001/_settings
205
205
{
206
206
"index" : {
207
207
"routing.allocation.total_shards_per_node" : 5
@@ -245,7 +245,7 @@ You can find these empty indices using the <<cat-count,cat count API>>.
245
245
246
246
[source,console]
247
247
----
248
- GET / _cat/count/my-index-000001?v=true
248
+ GET _cat/count/my-index-000001?v=true
249
249
----
250
250
// TEST[setup:my_index]
251
251
@@ -255,7 +255,7 @@ unneeded indices.
255
255
256
256
[source,console]
257
257
----
258
- DELETE / my-index-*
258
+ DELETE my-index-*
259
259
----
260
260
// TEST[setup:my_index]
261
261
@@ -270,7 +270,7 @@ are resource-intensive. If possible, run the force merge during off-peak hours.
270
270
271
271
[source,console]
272
272
----
273
- POST / my-index-000001/_forcemerge
273
+ POST my-index-000001/_forcemerge
274
274
----
275
275
// TEST[setup:my_index]
276
276
@@ -283,7 +283,7 @@ If you no longer write to an index, you can use the
283
283
284
284
[source,console]
285
285
----
286
- POST / my-index-000001/_shrink/my-shrunken-index-000001
286
+ POST my-index-000001/_shrink/my-shrunken-index-000001
287
287
----
288
288
// TEST[s/^/PUT my-index-000001\n{"settings":{"index.number_of_shards":2,"blocks.write":true}}\n/]
289
289
@@ -303,7 +303,7 @@ shared index pattern, such as `my-index-2099.10.11`, into a monthly
303
303
304
304
[source,console]
305
305
----
306
- POST / _reindex
306
+ POST _reindex
307
307
{
308
308
"source": {
309
309
"index": "my-index-2099.10.*"
0 commit comments