Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add wait_for_health=yellow to reindex snippets #18295

Merged
merged 1 commit into from
May 12, 2016
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/reference/docs/reindex.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ POST _reindex
}
--------------------------------------------------
// CONSOLE
// TEST[s/^/PUT twitter\nPUT blog\n/]
// TEST[s/^/PUT twitter\nPUT blog\nGET _cluster\/health?wait_for_status=yellow\n/]

It's also possible to limit the number of processed documents by setting
`size`. This will only copy a single document from `twitter` to
Expand Down Expand Up @@ -299,7 +299,7 @@ POST _reindex
}
--------------------------------------------------
// CONSOLE
// TEST[s/^/PUT source\n/]
// TEST[s/^/PUT source\nGET _cluster\/health?wait_for_status=yellow\n/]

By default `_reindex` uses scroll batches of 100. You can change the
batch size with the `size` field in the `source` element:
Expand All @@ -319,7 +319,7 @@ POST _reindex
}
--------------------------------------------------
// CONSOLE
// TEST[s/^/PUT source\n/]
// TEST[s/^/PUT source\nGET _cluster\/health?wait_for_status=yellow\n/]

Reindex can also use the <<ingest>> feature by specifying a
`pipeline` like this:
Expand All @@ -338,7 +338,7 @@ POST _reindex
}
--------------------------------------------------
// CONSOLE
// TEST[s/^/PUT source\n/]
// TEST[s/^/PUT source\nGET _cluster\/health?wait_for_status=yellow\n/]

[float]
=== URL Parameters
Expand Down Expand Up @@ -435,7 +435,7 @@ While Reindex is running you can fetch their status using the

[source,js]
--------------------------------------------------
GET _tasks/?pretty&detailed=true&actions=*reindex
GET _tasks?detailed=true&actions=*reindex
--------------------------------------------------
// CONSOLE

Expand Down Expand Up @@ -534,7 +534,7 @@ create an index containing documents that look like this:

[source,js]
--------------------------------------------------
POST test/test/1?refresh&pretty
POST test/test/1?refresh
{
"text": "words words",
"flag": "foo"
Expand All @@ -547,7 +547,7 @@ But you don't like the name `flag` and want to replace it with `tag`.

[source,js]
--------------------------------------------------
POST _reindex?pretty
POST _reindex
{
"source": {
"index": "test"
Expand All @@ -567,7 +567,7 @@ Now you can get the new document:

[source,js]
--------------------------------------------------
GET test2/test/1?pretty
GET test2/test/1
--------------------------------------------------
// CONSOLE
// TEST[continued]
Expand Down
4 changes: 2 additions & 2 deletions docs/reference/docs/update-by-query.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ types at once, just like the search API:
POST twitter,blog/tweet,post/_update_by_query
--------------------------------------------------
// CONSOLE
// TEST[s/^/PUT twitter\nPUT blog\n/]
// TEST[s/^/PUT twitter\nPUT blog\nGET _cluster\/health?wait_for_status=yellow\n/]

If you provide `routing` then the routing is copied to the scroll query,
limiting the process to the shards that match that routing value:
Expand Down Expand Up @@ -266,7 +266,7 @@ While Update By Query is running you can fetch their status using the

[source,js]
--------------------------------------------------
GET _tasks/?pretty&detailed=true&action=*byquery
GET _tasks?detailed=true&action=*byquery
--------------------------------------------------
// CONSOLE

Expand Down