Right, I was referring to Karussell's suggestion of using a timestamp
to allow regular (non-"scan") searches to return a consistent set of
results.
I want sorted results (rules out "scan") and I want to be able to page
through the results without missing documents or seeing duplicates.
Any suggestions, has this kind of request come up before?
Thanks,
Jamshid
On Oct 14, 7:23 am, Shay Banon kim...@gmail.com wrote:
Scan search type is a point in time search, when its executed. You won't see
changes (either deletions or new docs) after its first execution.On Thu, Oct 13, 2011 at 9:07 PM, Jamshid jamshi...@gmail.com wrote:
Interesting, I hadn't thought of that. So the timestamp would be the
"create date" of the document? Not sure how filtering would work when
updating or deleting documents, would elasticsearch keep the updated
record in the same "place" while paginating? But I don't see a
solution if documents are deleted while paging.
--JamshidOn Oct 12, 10:04 am, Karussell tableyourt...@googlemail.com wrote:
scan search type is limited:
Note scan search type does not support sorting (either on score or
a field) or faceting.You can just use a timestamp for every document and filter newer
documents away when doing pagination. (same procedure like twitter
handles it)On 7 Okt., 07:19, Jamshid jamshi...@gmail.com wrote:
One thing to keep in mind is that if you are continuously indexing,
don't expect to be able to page through the results without missing
some items or seeing duplicates.You can use the "scan" search type (
Elasticsearch Platform — Find real-time answers at scale | Elastic
reference/api/search/search-type.html) instead if you want a
consistent result set that you can page through, but unfortunately you
will not be able to sort the results when using "scan".--Jamshid
On Oct 6, 9:34 am, Benjamin Devèze benjamin.dev...@gmail.com wrote:
Yeah you will be happy it does contain the total result count.