honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-08 22:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Document refresh for reindex and friends

Browse Source 
Reindex and friends don't support `refresh=wait_for` and this documents
that.
This commit is contained in:
Nik Everett 2018-10-29 13:58:55 -04:00
parent c9a8c58039
commit 3051e37e45
3 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/reference/docs/delete-by-query.asciidoc
View File

@ -147,7 +147,7 @@ and `scroll`.
Sending the `refresh` will refresh all shards involved in the delete by query Sending the `refresh` will refresh all shards involved in the delete by query
once the request completes. This is different than the Delete API's `refresh` once the request completes. This is different than the Delete API's `refresh`
parameter which causes just the shard that received the delete request parameter which causes just the shard that received the delete request
to be refreshed. to be refreshed. Also unlike the Delete API it does not support `wait_for`.
If the request contains `wait_for_completion=false` then Elasticsearch will If the request contains `wait_for_completion=false` then Elasticsearch will
perform some preflight checks, launch the request, and then return a `task` perform some preflight checks, launch the request, and then return a `task`

3
docs/reference/docs/reindex.asciidoc
View File

@ -527,7 +527,8 @@ supports `refresh`, `wait_for_completion`, `wait_for_active_shards`, `timeout`,
Sending the `refresh` url parameter will cause all indexes to which the request Sending the `refresh` url parameter will cause all indexes to which the request
wrote to be refreshed. This is different than the Index API's `refresh` wrote to be refreshed. This is different than the Index API's `refresh`
parameter which causes just the shard that received the new data to be refreshed. parameter which causes just the shard that received the new data to be
refreshed. Also unlike the Index API it does not support `wait_for`.
If the request contains `wait_for_completion=false` then Elasticsearch will If the request contains `wait_for_completion=false` then Elasticsearch will
perform some preflight checks, launch the request, and then return a `task` perform some preflight checks, launch the request, and then return a `task`

3
docs/reference/docs/update-by-query.asciidoc
View File

@ -203,8 +203,9 @@ also supports `refresh`, `wait_for_completion`, `wait_for_active_shards`, `timeo
and `scroll`. and `scroll`.
Sending the `refresh` will update all shards in the index being updated when Sending the `refresh` will update all shards in the index being updated when
the request completes. This is different than the Index API's `refresh` the request completes. This is different than the Update API's `refresh`
parameter which causes just the shard that received the new data to be indexed. parameter which causes just the shard that received the new data to be indexed.
Also unlike the Update API it does not support `wait_for`.
If the request contains `wait_for_completion=false` then Elasticsearch will If the request contains `wait_for_completion=false` then Elasticsearch will
perform some preflight checks, launch the request, and then return a `task` perform some preflight checks, launch the request, and then return a `task`