Closed artemmukhin closed 10 months ago
Describe the bug
SearchClient.deleteScroll method sends a DELETE request to an incorrect path: /scroll/<id> instead of /_search/scroll/<id> (see docs).
SearchClient.deleteScroll
/scroll/<id>
/_search/scroll/<id>
This also affects SearchClient.scroll(response: SearchResponse), which is expected to delete the scroll at the end by using SearchClient.deleteScroll.
SearchClient.scroll(response: SearchResponse)
To Reproduce
SearchClient.deleteScroll(id)
SearchClient.scroll(id)
Expected: 404: No search context found for id Actual: the next batch of search results is returned
404: No search context found for id
Will you be able to help with a pull request?
I am going to open a PR that fixes the SearchClient.deleteScroll implementation right away.
Thanks for this! Somehow this slipped through. I think searchAfter is recommended now, which is what I mostly use.
Describe the bug
SearchClient.deleteScroll
method sends a DELETE request to an incorrect path:/scroll/<id>
instead of/_search/scroll/<id>
(see docs).This also affects
SearchClient.scroll(response: SearchResponse)
, which is expected to delete the scroll at the end by usingSearchClient.deleteScroll
.To Reproduce
SearchClient.deleteScroll(id)
SearchClient.scroll(id)
.Expected:
404: No search context found for id
Actual: the next batch of search results is returnedWill you be able to help with a pull request?
I am going to open a PR that fixes the
SearchClient.deleteScroll
implementation right away.