Apologies in advance for hijacking the thread, but somewhat related, does anyone have experience with using cursorMark and elevations at the same time? When I tried this, either passing elevatedIds via solrJ or specifying them in elevate.xml, I got an AIOOBE if a cursorMark was also specified. When I get a chance, I'll try to reproduce in a unit test. Just wondering if anyone has encountered this and has a workaround. This is the one thing that is stopping us adopting cursor-based pagination :-(
Cheers, -Brendan On 28 January 2015 at 02:51, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : But my concern is if solr internally creates a different set for > each > : and every different queries upon sort values and they lasts for ever I > : think. > > > https://cwiki.apache.org/confluence/display/solr/Pagination+of+Results > > "Cursors in Solr are a logical concept, that doesn't involve caching any > state information on the server. Instead the sort values of the last > document returned to the client are used to compute a "mark" representing > a logical point in the ordered space of sort values." > > > > > -Hoss > http://www.lucidworks.com/ >
