Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Made APIs consistently accept a query in the request body's
query
f…
…ield. The following APIs now accept the query in a top level `query` field like: * delete_by_query * validate_query * count These APIs used to accept the query directly in the request body which was inconsistent with the search and explain APIs. For this reason t Closes #4074
- Loading branch information
Showing
36 changed files
with
351 additions
and
303 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -28,8 +28,9 @@ | |
delete_by_query: | ||
index: test_1 | ||
body: | ||
match: | ||
foo: bar | ||
query: | ||
match: | ||
foo: bar | ||
|
||
- is_true: ok | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
bb01995
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we also make all APIs take it as form encoded post parameter. GET parameter may have size issue when a large query needs to be passed.
The reason is that some client side frameworks (ex. ExtJs) do not work with post body wery well relying on form encoded parameters instead
bb01995
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @roytmana this is unrelated to this commit, which is about consistently supporting
query
json field in request body. If you think that supporting form encoded post parameters is needed then I suggest you open a dedicated issue for it.