We are using scroll to do paging.
We are encountering an issue where the last result from the initial search
appears as the first result in our scroll request.
so.. hits[length-1] == nextPageHits[0]
This only seems to occur after we do a large series of writes and searches.
Initially it
would also like to know...
On Friday, November 14, 2014 9:29:54 AM UTC-7, Todd Nine wrote:
Hey All,
I have a question about the internal implementation of geo hashes and
distance filters. Here is my current understanding, I'm struggling to
figure out how to apply these to our queries
