if by "old behavior" you mean incremending the start param then the the
order of results when doing concurrent indexing was always dependent on
what exactly your sort was.
when using a cursor, the impacts of concurrent indexing are also dependent
on what your sort clause looks like -- but in d
Hi,
I have a quick question about this new implementation - in the old
implementation AFAIK, in a real-time indexing scenario, the results gathered
from paging would not be consecutive.
Meaning you would ask for 50 docs, new docs arrive, when you ask for the next
50 docs - you get an arbitrary
