-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Add POST /_search/clear_scroll endpoint and deprecate delete scroll endpoint #21510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why add this at all? This will result in adding a new method to the clients.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is it just there for bwc testing?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. no you are right. it is a leftover, due to the fact that I had thought POST shouldn't support the query_string parameter at all, now that it does, I can get right of this new api.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. oh wait though, DELETE is done against _search/scroll while POST is done against _search/clear_scroll . I don't think we can express that in our spec without having two apis. POST _search/scroll is already taken by the search api. |
||
| "delete_scroll": { | ||
| "documentation": "https://www.elastic.co/guide/en/elasticsearch/reference/5.x/search-request-scroll.html", | ||
| "methods": ["DELETE"], | ||
| "url": { | ||
| "path": "/_search/scroll/{scroll_id}", | ||
| "paths": ["/_search/scroll/{scroll_id}", "/_search/scroll"], | ||
| "parts": { | ||
| "scroll_id": { | ||
| "type" : "list", | ||
| "description" : "A comma-separated list of scroll IDs to clear" | ||
| } | ||
| }, | ||
| "params": {} | ||
| }, | ||
| "body": { | ||
| "description": "A comma-separated list of scroll IDs to clear, has precedence over the scroll_id parameter" | ||
| } | ||
| } | ||
| } | ||
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.
this one looks a bit odd, looked better providing _all as part of the url, but maybe that's ok
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.
Perhaps this could be replaced with supporting
*as a scroll IDThere 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.
Actually we probably don't support wildcard matching, so using
_allis better