I might have been wrong there. Having an explicit check for the # results returned vs rows requested, would allow you to avoid the last request that would otherwise come back with 0 results. That check isn’t automatically done within Solr.
Anshum > On Jun 19, 2018, at 2:39 PM, Anshum Gupta <ansh...@apple.com> wrote: > > Hi David, > > The cursormark would be the same if you get back fewer than the max records > requested and so you should exit, as per the documentation. > > I think the documentation says just what you are suggesting, but if you think > it could be improved, feel free to put up a patch. > > > Anshum > > >> On Jun 18, 2018, at 2:09 AM, David Frese <david.fr...@active-group.de >> <mailto:david.fr...@active-group.de>> wrote: >> >> Hi List, >> >> the documentation of 'cursorMarks' recommends to fetch until a query returns >> the cursorMark that was passed in to a request. >> >> But that always requires an additional request at the end, so I wonder if I >> can stop already, if a request returns less results than requested (num >> rows). There won't be new documents added during the search in my use case, >> so could there every be a non-empty 'page' after a non-full 'page'? >> >> Thanks very much. >> >> -- >> David Frese >> +49 7071 70896 75 >> >> Active Group GmbH >> Hechinger Str. 12/1, 72072 Tübingen >> Registergericht: Amtsgericht Stuttgart, HRB 224404 >> Geschäftsführer: Dr. Michael Sperber >
signature.asc
Description: Message signed with OpenPGP
