You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using nest to scroll through a scan query.
Nest sends a request using the url: http://{address}:9200/_search/scroll?scroll=10m&scroll_id={scroll_id}
The scroll_id gets longer if you have a lot of shards. For me, with 500 shards, I get an id of length 20708. This causes the last parts of the scroll_id to be thrown away when added to the url.
Sadly the .NET HttpWebClient doesn't allow for a body data when doing a GET but luckily elasticsearch allows you to do a POST with BODY for almost every GET that has a BODY so the .Scroll() now does a POST.
It still passes the unit/integration tests so be sure to report back once the nest release is out.
I'm using nest to scroll through a scan query.
Nest sends a request using the url: http://{address}:9200/_search/scroll?scroll=10m&scroll_id={scroll_id}
The scroll_id gets longer if you have a lot of shards. For me, with 500 shards, I get an id of length 20708. This causes the last parts of the scroll_id to be thrown away when added to the url.
Would using the syntax from here: http://www.elasticsearch.org/guide/reference/api/search/search-type/
solve the problem?
It would look like this:
curl -XGET 'localhost:9200/_search/scroll?scroll=10m' -d '{scroll_id}'
The text was updated successfully, but these errors were encountered: