Chris Hostetter has a writeup here that has a good explanation: https://lucidworks.com/2013/12/12/coming-soon-to-solr-efficient-cursor-based-iteration-of-large-result-sets/
Best, Erick On Tue, Jul 18, 2017 at 10:00 PM, suresh pendap <sureshfors...@gmail.com> wrote: > Hi, > > This question is more about the Implementation detail of the cursorMark > feature. > > I was reading about using the cursorMark feature for deep pagination in > Solr mentioned in this blog http://yonik.com/solr/paging-and-deep-paging/ > > It is not clear to me as to how it is more efficient as compared to the > regular pagination. > > The blog says that there is no state maintained on the server side. > > If there is no state maintained then where does it get its efficiency from? > > Assuming that it does maintain the state on the server side, does the next > page request has to go the same aggregator node which had served the first > page? > > > Thanks > Suresh
