DELETE /_search/scroll - not working - do we care?

[ranguard]

This doesn't seem to have ever worked... we don't support DELETE for /_search

Maybe not an issue? - Now we have a newer ElasticSearch and more capacity.

I have setup fastly (CDN) to return a 200 fakes response {} and make sure this doesn't get to our servers for /_search/scroll - for now, so that error logs are easier to look at, so our origin's won't get these requests at the moment

NOTE: SECURITY

• This could open a security hole if not done correctly!
• Create search_DELETE() end point and allow only access to delete scrolly things

[reyjrar]

We could, in theory intercept the scroll timeout and rewrite the timeout to a very low number to prevent scrolls tying up too many resources. Per the Elastic docs, we only need to the scroll to be alive between scroll calls as each scroll call resets the scroll expiry, see the Elastic scroll docs for more information.