Fixed bad asciidoc in delete-by-query
This commit is contained in:
parent
033defee9a
commit
78d3028bb7
|
@ -294,7 +294,7 @@ GET /_tasks/taskId:1
|
||||||
|
|
||||||
The advantage of this API is that it integrates with `wait_for_completion=false`
|
The advantage of this API is that it integrates with `wait_for_completion=false`
|
||||||
to transparently return the status of completed tasks. If the task is completed
|
to transparently return the status of completed tasks. If the task is completed
|
||||||
and `wait_for_completion=false` was set on it then it'll come back with
|
and `wait_for_completion=false` was set on it then it'll come back with
|
||||||
`results` or an `error` field. The cost of this feature is the document that
|
`results` or an `error` field. The cost of this feature is the document that
|
||||||
`wait_for_completion=false` creates at `.tasks/task/${taskId}`. It is up to
|
`wait_for_completion=false` creates at `.tasks/task/${taskId}`. It is up to
|
||||||
you to delete that document.
|
you to delete that document.
|
||||||
|
@ -467,6 +467,7 @@ Which results in a sensible `total` like this one:
|
||||||
|
|
||||||
Adding `slices` to `_delete_by_query` just automates the manual process used in
|
Adding `slices` to `_delete_by_query` just automates the manual process used in
|
||||||
the section above, creating sub-requests which means it has some quirks:
|
the section above, creating sub-requests which means it has some quirks:
|
||||||
|
|
||||||
* You can see these requests in the
|
* You can see these requests in the
|
||||||
<<docs-delete-by-query-task-api,Tasks APIs>>. These sub-requests are "child"
|
<<docs-delete-by-query-task-api,Tasks APIs>>. These sub-requests are "child"
|
||||||
tasks of the task for the request with `slices`.
|
tasks of the task for the request with `slices`.
|
||||||
|
|
Loading…
Reference in New Issue