Remove `GET` option for /_forcemerge

POST should be used to indicate this is not just a retrieval operation.

Resolves #15165
This commit is contained in:
Lee Hinman 2015-12-03 12:03:07 -07:00
parent d2e07f21e0
commit f709b7283f
3 changed files with 4 additions and 4 deletions

View File

@ -45,9 +45,6 @@ public class RestForceMergeAction extends BaseRestHandler {
super(settings, controller, client);
controller.registerHandler(POST, "/_forcemerge", this);
controller.registerHandler(POST, "/{index}/_forcemerge", this);
controller.registerHandler(GET, "/_forcemerge", this);
controller.registerHandler(GET, "/{index}/_forcemerge", this);
}
@Override

View File

@ -90,6 +90,9 @@ The search exists api has been removed in favour of using the search api with
The deprecated `/_optimize` endpoint has been removed. The `/_forcemerge`
endpoint should be used in lieu of optimize.
The `GET` HTTP verb for `/_forcemerge` is no longer supported, please use the
`POST` HTTP verb.
==== Deprecated queries removed
The following deprecated queries have been removed:

View File

@ -1,7 +1,7 @@
{
"indices.forcemerge": {
"documentation": "http://www.elastic.co/guide/en/elasticsearch/reference/master/indices-forcemerge.html",
"methods": ["POST", "GET"],
"methods": ["POST"],
"url": {
"path": "/_forcemerge",
"paths": ["/_forcemerge", "/{index}/_forcemerge"],