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
: 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 cach
On Tue, Jan 27, 2015 at 3:29 AM, CKReddy Bhimavarapu
wrote:
> Hi,
> Using CursorMark we over come the Deep paging so far so good. As far
> as I understand cursormark unique for each and every query depending on
> sort values other than unique id and also depends up on number of rows.
> B
Hi,
Using CursorMark we over come the Deep paging so far so good. As far
as I understand cursormark unique for each and every query depending on
sort values other than unique id and also depends up on number of rows.
But my concern is if solr internally creates a different set for each
an
