[Docs] Reproduce #209403 in new API docs (#216439)

This change reproduces the asciidoc change made in
https://github.com/elastic/kibana/pull/209403 into the new API docs.
It'll be picked up the next time the API docs output is generated and
refreshed.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
This commit is contained in:
florent-leborgne 2025-04-01 18:21:43 +02:00 committed by GitHub
parent bcd68b1100
commit b7d1141b6b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 6 additions and 4 deletions

View file

@ -49876,7 +49876,8 @@ paths:
/api/upgrade_assistant/reindex/batch:
post:
description: |
Start or resume multiple reindexing tasks in one request. Additionally, reindexing tasks started or resumed via the batch endpoint will be placed on a queue and run one-by-one, which ensures that minimal cluster resources are consumed over time.
Start or resume multiple reindexing tasks in one request. Additionally, [reindexing](https://www.elastic.co/docs/api/doc/kibana/operation/operation-start-upgrade-reindex) tasks for upgrading indices that are started or resumed via the batch endpoint will be placed on a queue and executed one-by-one. This ensures that minimal cluster resources are consumed over time.
Note that this API does not support data streams.
operationId: batch-start-upgrade-reindex
requestBody:
content:
@ -49962,7 +49963,6 @@ paths:
summary: Batch start or resume reindexing
tags:
- upgrade
x-state: Technical Preview
/api/upgrade_assistant/reindex/batch/queue:
get:
description: |

View file

@ -259,8 +259,10 @@ paths:
summary: Batch start or resume reindexing
description: >
Start or resume multiple reindexing tasks in one request.
Additionally, reindexing tasks started or resumed via the batch endpoint will be placed on a queue and run one-by-one, which ensures that minimal cluster resources are consumed over time.
x-state: Technical Preview
Additionally, [reindexing](https://www.elastic.co/docs/api/doc/kibana/operation/operation-start-upgrade-reindex) tasks for upgrading indices that are started or resumed via the batch endpoint will be placed on a queue and executed one-by-one.
This ensures that minimal cluster resources are consumed over time.
Note that this API does not support data streams.
operationId: batch-start-upgrade-reindex
tags:
- upgrade