summaryrefslogtreecommitdiff
path: root/docs/reference
diff options
context:
space:
mode:
authorJun Ohtani <johtani@gmail.com>2016-10-27 17:43:18 +0900
committerGitHub <noreply@github.com>2016-10-27 17:43:18 +0900
commita66c76eb446fed55efa7ad12f97923c248ff96d4 (patch)
tree8661f8187e47045bd9c8ef5ca32e85baf209f186 /docs/reference
parentc1a9833445114c3490fe09300a2e3ce0c37cc97a (diff)
parent945fa499d223261fffc89c732f340ad112ae58d7 (diff)
Merge pull request #20704 from johtani/remove_request_params_in_analyze_api
Removing request parameters in _analyze API
Diffstat (limited to 'docs/reference')
-rw-r--r--docs/reference/indices/analyze.asciidoc15
-rw-r--r--docs/reference/mapping/params/analyzer.asciidoc6
-rw-r--r--docs/reference/migration/migrate_6_0/rest.asciidoc4
3 files changed, 8 insertions, 17 deletions
diff --git a/docs/reference/indices/analyze.asciidoc b/docs/reference/indices/analyze.asciidoc
index dbb2c8f101..0d9d60d484 100644
--- a/docs/reference/indices/analyze.asciidoc
+++ b/docs/reference/indices/analyze.asciidoc
@@ -100,21 +100,6 @@ curl -XGET 'localhost:9200/test/_analyze' -d '
Will cause the analysis to happen based on the analyzer configured in the
mapping for `obj1.field1` (and if not, the default index analyzer).
-All parameters can also supplied as request parameters. For example:
-
-[source,js]
---------------------------------------------------
-curl -XGET 'localhost:9200/_analyze?tokenizer=keyword&filter=lowercase&text=this+is+a+test'
---------------------------------------------------
-
-For backwards compatibility, we also accept the text parameter as the body of the request,
-provided it doesn't start with `{` :
-
-[source,js]
---------------------------------------------------
-curl -XGET 'localhost:9200/_analyze?tokenizer=keyword&filter=lowercase&char_filter=html_strip' -d 'this is a <b>test</b>'
---------------------------------------------------
-
=== Explain Analyze
If you want to get more advanced details, set `explain` to `true` (defaults to `false`). It will output all token attributes for each token.
diff --git a/docs/reference/mapping/params/analyzer.asciidoc b/docs/reference/mapping/params/analyzer.asciidoc
index c075b66280..0b60451e02 100644
--- a/docs/reference/mapping/params/analyzer.asciidoc
+++ b/docs/reference/mapping/params/analyzer.asciidoc
@@ -60,13 +60,15 @@ PUT /my_index
}
}
-GET my_index/_analyze?field=text <3>
+GET my_index/_analyze <3>
{
+ "field": "text",
"text": "The quick Brown Foxes."
}
-GET my_index/_analyze?field=text.english <4>
+GET my_index/_analyze <4>
{
+ "field": "text.english",
"text": "The quick Brown Foxes."
}
--------------------------------------------------
diff --git a/docs/reference/migration/migrate_6_0/rest.asciidoc b/docs/reference/migration/migrate_6_0/rest.asciidoc
index a0ac594e3f..897b3a53e8 100644
--- a/docs/reference/migration/migrate_6_0/rest.asciidoc
+++ b/docs/reference/migration/migrate_6_0/rest.asciidoc
@@ -7,3 +7,7 @@ In previous versions of Elasticsearch, JSON documents were allowed to contain un
This feature was removed in the 5.x series, but a backwards-compatibility layer was added via the
system property `elasticsearch.json.allow_unquoted_field_names`. This backwards-compatibility layer
has been removed in Elasticsearch 6.0.0.
+
+==== Analyze API changes
+
+The deprecated request parameters and plain text in request body has been removed. Define parameters in request body.