honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-03-25 09:28:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add wait_for_health=yellow to reindex snippets

Browse Source 
This should help the tests pass more consistently. Should.

This also removes from `?pretty` from the docs. It isn't a thing
with `// CONSOLE`.

Relates to
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-os-compatibility/os=oraclelinux/399/console
This commit is contained in:
Nik Everett 2016-05-12 12:20:06 -04:00
parent 5ee5cc25cc
commit 94317b1d33
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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
@ -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:
@ -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:
@ -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
@ -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
@ -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"
@ -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"
@ -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]

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

@ -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:
@ -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