Browse Source

Docs: Document refresh for reindex and friends

Reindex and friends don't support `refresh=wait_for` and this documents
that.
Nik Everett 7 năm trước cách đây
mục cha
commit
3051e37e45

+ 1 - 1
docs/reference/docs/delete-by-query.asciidoc

@@ -147,7 +147,7 @@ and `scroll`.
 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`
 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
 perform some preflight checks, launch the request, and then return a `task`

+ 2 - 1
docs/reference/docs/reindex.asciidoc

@@ -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
 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
 perform some preflight checks, launch the request, and then return a `task`

+ 2 - 1
docs/reference/docs/update-by-query.asciidoc

@@ -203,8 +203,9 @@ also supports `refresh`, `wait_for_completion`, `wait_for_active_shards`, `timeo
 and `scroll`.
 
 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.
+Also unlike the Update API it does not support `wait_for`.
 
 If the request contains `wait_for_completion=false` then Elasticsearch will
 perform some preflight checks, launch the request, and then return a `task`