Remove wait_for_status=yellow from the docs

It is no longer required after 687e2e12b3.
2016-07-15 16:02:07 -04:00 · 2016-07-15 16:02:07 -04:00 · 7aeea764ba
parent 6acb8b31fc
commit 7aeea764ba
27 changed files with 10 additions and 106 deletions
--- a/buildSrc/src/main/groovy/org/elasticsearch/gradle/doc/RestTestsFromSnippetsTask.groovy
+++ b/buildSrc/src/main/groovy/org/elasticsearch/gradle/doc/RestTestsFromSnippetsTask.groovy
@ -184,13 +184,6 @@ public class RestTestsFromSnippetsTask extends SnippetsTask {
            current.println('---')
            current.println("setup:")
            body(setup, true)
-            // always wait for yellow before anything is executed
-            current.println(
-                    "  - do:\n" +
-                    "      raw:\n" +
-                    "        method: GET\n" +
-                    "        path: \"_cluster/health\"\n" +
-                    "        wait_for_status: \"yellow\"")
        }

        private void body(Snippet snippet, boolean inSetup) {
--- a/docs/plugins/analysis-icu.asciidoc
+++ b/docs/plugins/analysis-icu.asciidoc
@ -161,8 +161,6 @@ PUT icu_sample
    }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST icu_sample/_analyze?analyzer=my_analyzer&text=Elasticsearch. Wow!
 --------------------------------------------------
 // CONSOLE
@ -360,8 +358,6 @@ PUT /my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 GET _search <3>
 {
  "query": {
@ -481,8 +477,6 @@ PUT icu_sample
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 GET icu_sample/_analyze?analyzer=latin
 {
  "text": "你好" <2>
--- a/docs/plugins/analysis-kuromoji.asciidoc
+++ b/docs/plugins/analysis-kuromoji.asciidoc
@ -172,8 +172,6 @@ PUT kuromoji_sample
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST kuromoji_sample/_analyze?analyzer=my_analyzer&text=東京スカイツリー
 --------------------------------------------------
 // CONSOLE
@ -226,8 +224,6 @@ PUT kuromoji_sample
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST kuromoji_sample/_analyze?analyzer=my_analyzer&text=飲み
 --------------------------------------------------
 // CONSOLE
@ -286,8 +282,6 @@ PUT kuromoji_sample
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST kuromoji_sample/_analyze?analyzer=my_analyzer&text=寿司がおいしいね

 --------------------------------------------------
@ -360,8 +354,6 @@ PUT kuromoji_sample
    }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST kuromoji_sample/_analyze?analyzer=katakana_analyzer&text=寿司 <1>

 POST kuromoji_sample/_analyze?analyzer=romaji_analyzer&text=寿司 <2>
@ -413,8 +405,6 @@ PUT kuromoji_sample
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST kuromoji_sample/_analyze?analyzer=my_analyzer&text=コピー <1>

 POST kuromoji_sample/_analyze?analyzer=my_analyzer&text=サーバー <2>
@ -464,8 +454,6 @@ PUT kuromoji_sample
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST kuromoji_sample/_analyze?analyzer=analyzer_with_ja_stop&text=ストップは消える
 --------------------------------------------------
 // CONSOLE
@ -512,8 +500,6 @@ PUT kuromoji_sample
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST kuromoji_sample/_analyze?analyzer=my_analyzer&text=一〇〇〇

 --------------------------------------------------
--- a/docs/plugins/analysis-phonetic.asciidoc
+++ b/docs/plugins/analysis-phonetic.asciidoc
@ -79,8 +79,6 @@ PUT phonetic_sample
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST phonetic_sample/_analyze?analyzer=my_analyzer&text=Joe Bloggs <1>
 --------------------------------------------------
 // CONSOLE
--- a/docs/reference/analysis/analyzers/configuring.asciidoc
+++ b/docs/reference/analysis/analyzers/configuring.asciidoc
@ -38,8 +38,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "field": "my_text", <2>
@ -98,4 +96,3 @@ POST my_index/_analyze
 // TESTRESPONSE

 /////////////////////
-
--- a/docs/reference/analysis/analyzers/custom-analyzer.asciidoc
+++ b/docs/reference/analysis/analyzers/custom-analyzer.asciidoc
@ -74,8 +74,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_custom_analyzer",
@ -196,8 +194,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_custom_analyzer",
@ -258,4 +254,3 @@ The above example produces the following terms:
 ---------------------------
 [ i'm, _happy_, person, you ]
 ---------------------------
-
--- a/docs/reference/analysis/analyzers/fingerprint-analyzer.asciidoc
+++ b/docs/reference/analysis/analyzers/fingerprint-analyzer.asciidoc
@ -114,8 +114,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_fingerprint_analyzer",
--- a/docs/reference/analysis/analyzers/pattern-analyzer.asciidoc
+++ b/docs/reference/analysis/analyzers/pattern-analyzer.asciidoc
@ -195,8 +195,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_email_analyzer",
@ -285,8 +283,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 GET my_index/_analyze
 {
  "analyzer": "camel",
--- a/docs/reference/analysis/analyzers/standard-analyzer.asciidoc
+++ b/docs/reference/analysis/analyzers/standard-analyzer.asciidoc
@ -179,8 +179,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_english_analyzer",
@ -278,4 +276,3 @@ The above example produces the following terms:
 ---------------------------
 [ 2, quick, brown, foxes, jumpe, d, over, lazy, dog's, bone ]
 ---------------------------
-
--- a/docs/reference/analysis/analyzers/stop-analyzer.asciidoc
+++ b/docs/reference/analysis/analyzers/stop-analyzer.asciidoc
@ -154,8 +154,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_stop_analyzer",
@ -240,5 +238,3 @@ The above example produces the following terms:
 ---------------------------
 [ quick, brown, foxes, jumped, lazy, dog, s, bone ]
 ---------------------------
-
-
--- a/docs/reference/analysis/charfilters/htmlstrip-charfilter.asciidoc
+++ b/docs/reference/analysis/charfilters/htmlstrip-charfilter.asciidoc
@ -93,8 +93,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
@ -130,6 +128,3 @@ The above example produces the following term:
 ---------------------------
 [ \nI'm so <b>happy</b>!\n ]
 ---------------------------
-
-
-
--- a/docs/reference/analysis/charfilters/mapping-charfilter.asciidoc
+++ b/docs/reference/analysis/charfilters/mapping-charfilter.asciidoc
@ -66,8 +66,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
@ -134,8 +132,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
--- a/docs/reference/analysis/charfilters/pattern-replace-charfilter.asciidoc
+++ b/docs/reference/analysis/charfilters/pattern-replace-charfilter.asciidoc
@ -58,8 +58,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
@ -123,8 +121,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
--- a/docs/reference/analysis/testing.asciidoc
+++ b/docs/reference/analysis/testing.asciidoc
@ -69,8 +69,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 GET my_index/_analyze <3>
 {
  "analyzer": "std_folded", <4>
--- a/docs/reference/analysis/tokenizers/classic-tokenizer.asciidoc
+++ b/docs/reference/analysis/tokenizers/classic-tokenizer.asciidoc
@ -164,8 +164,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
@ -264,6 +262,3 @@ The above example produces the following terms:
 ---------------------------
 [ The, 2, QUICK, Brown, Foxes, jumpe, d, over, the, lazy, dog's, bone ]
 ---------------------------
-
-
-
--- a/docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc
+++ b/docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc
@ -128,8 +128,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
@ -319,5 +317,3 @@ GET my_index/_search
 ----------------------------
 // TESTRESPONSE[s/"took".*/"took": "$body.took",/]
 /////////////////////
-
-
--- a/docs/reference/analysis/tokenizers/ngram-tokenizer.asciidoc
+++ b/docs/reference/analysis/tokenizers/ngram-tokenizer.asciidoc
@ -230,8 +230,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
@ -302,5 +300,3 @@ The above example produces the following terms:
 ---------------------------
 [ Qui, uic, ick, Fox, oxe, xes ]
 ---------------------------
-
-
--- a/docs/reference/analysis/tokenizers/pathhierarchy-tokenizer.asciidoc
+++ b/docs/reference/analysis/tokenizers/pathhierarchy-tokenizer.asciidoc
@ -114,8 +114,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
@ -172,4 +170,3 @@ If we were to set `reverse` to `true`, it would produce the following:
 ---------------------------
 [ one/two/three/, two/three/, three/ ]
 ---------------------------
-
--- a/docs/reference/analysis/tokenizers/pattern-tokenizer.asciidoc
+++ b/docs/reference/analysis/tokenizers/pattern-tokenizer.asciidoc
@ -130,8 +130,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
@ -223,8 +221,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
--- a/docs/reference/analysis/tokenizers/standard-tokenizer.asciidoc
+++ b/docs/reference/analysis/tokenizers/standard-tokenizer.asciidoc
@ -155,8 +155,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
@ -269,6 +267,3 @@ The above example produces the following terms:
 ---------------------------
 [ The, 2, QUICK, Brown, Foxes, jumpe, d, over, the, lazy, dog's, bone ]
 ---------------------------
-
-
-
--- a/docs/reference/analysis/tokenizers/uaxurlemail-tokenizer.asciidoc
+++ b/docs/reference/analysis/tokenizers/uaxurlemail-tokenizer.asciidoc
@ -111,8 +111,6 @@ PUT my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 POST my_index/_analyze
 {
  "analyzer": "my_analyzer",
--- a/docs/reference/docs/delete-by-query.asciidoc
+++ b/docs/reference/docs/delete-by-query.asciidoc
@ -101,7 +101,7 @@ POST twitter,blog/tweet,post/_delete_by_query
 }
 --------------------------------------------------
 // CONSOLE
-// TEST[s/^/PUT twitter\nPUT blog\nGET _cluster\/health?wait_for_status=yellow\n/]
+// TEST[s/^/PUT twitter\nPUT blog\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:
--- a/docs/reference/docs/reindex.asciidoc
+++ b/docs/reference/docs/reindex.asciidoc
@ -178,7 +178,7 @@ POST _reindex
 }
 --------------------------------------------------
 // CONSOLE
-// TEST[s/^/PUT twitter\nPUT blog\nGET _cluster\/health?wait_for_status=yellow\n/]
+// TEST[s/^/PUT twitter\nPUT blog\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
@ -320,7 +320,7 @@ POST _reindex
 }
 --------------------------------------------------
 // CONSOLE
-// TEST[s/^/PUT source\nGET _cluster\/health?wait_for_status=yellow\n/]
+// TEST[s/^/PUT source\n/]

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

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

 [float]
 === Reindex from Remote
@ -390,7 +390,7 @@ POST _reindex
 --------------------------------------------------
 // CONSOLE
 // TEST[setup:host]
-// TEST[s/^/PUT source\nGET _cluster\/health?wait_for_status=yellow\n/]
+// TEST[s/^/PUT source\n/]
 // TEST[s/otherhost:9200",/\${host}"/]
 // TEST[s/"username": "user",//]
 // TEST[s/"password": "pass"//]
--- a/docs/reference/docs/update-by-query.asciidoc
+++ b/docs/reference/docs/update-by-query.asciidoc
@ -156,7 +156,7 @@ types at once, just like the search API:
 POST twitter,blog/tweet,post/_update_by_query
 --------------------------------------------------
 // CONSOLE
-// TEST[s/^/PUT twitter\nPUT blog\nGET _cluster\/health?wait_for_status=yellow\n/]
+// TEST[s/^/PUT twitter\nPUT blog\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:
--- a/docs/reference/mapping/params/analyzer.asciidoc
+++ b/docs/reference/mapping/params/analyzer.asciidoc
@ -60,8 +60,6 @@ PUT /my_index
  }
 }

-GET _cluster/health?wait_for_status=yellow
-
 GET my_index/_analyze?field=text <3>
 {
  "text": "The quick Brown Foxes."
--- a/docs/reference/migration/migrate_5_0/mapping.asciidoc
+++ b/docs/reference/migration/migrate_5_0/mapping.asciidoc
@ -224,7 +224,7 @@ POST _reindex
 }
 ---------------
 // CONSOLE
-// TEST[s/^/PUT oldindex\nGET _cluster\/health?wait_for_status=yellow\n/]
+// TEST[s/^/PUT oldindex\n/]

 You can replace `_ttl` with time based index names (preferred) or by adding a
 cron job which runs a delete-by-query on a timestamp field in the source
--- a/docs/reference/search/request/sort.asciidoc
+++ b/docs/reference/search/request/sort.asciidoc
@ -26,8 +26,6 @@ PUT /my_index
        }
    }
 }
-
-GET /_cluster/health?wait_for_status=yellow
 --------------------------------------------------
 // CONSOLE