[
https://issues.apache.org/jira/browse/SOLR-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844861#comment-13844861
]
Steve Rowe commented on SOLR-5463:
----------------------------------
{quote}
One other comment i got from a coworker offline was why I liked cursorContinue
instead of nextCursor or cursorNext. My thinking was that since 'cursor', (as a
concept) is a noun, "next cursor" might suggest that it was a (different)
cursor then the one currently in use. I don't want people to think these
strings are names of cursors, and they re-use the same name until they are done
with it. I want to make it clear that to continue fetching results from this
cursor, you have to specify the new value.
Would "cursorAdvance" convey that better then cursorContinue ?
{quote}
You want to convey a (resumption) position in a result sequence. A cursor is
not itself a position; it's a movable pointer to a position. The value of the
{{cursor}} param is not the cursor itself; rather, it's the position from which
to resume iterating over a result sequence.
The problem as I see it is that the cursor itself has to be anonymous, since
the implementation stores no server-side state; passing in an opaque label thus
is not possible. So you're asking people to understand that they're moving a
thing-that-can't-have-a-fixed-label, and that's cognitively dissonant.
Maybe "continuation"/"nextContinuation" or "continue"/"nextContinue" or
"pos"/"nextPos"? (I don't love any of them.)
> Provide cursor/token based "searchAfter" support that works with arbitrary
> sorting (ie: "deep paging")
> ------------------------------------------------------------------------------------------------------
>
> Key: SOLR-5463
> URL: https://issues.apache.org/jira/browse/SOLR-5463
> Project: Solr
> Issue Type: New Feature
> Reporter: Hoss Man
> Assignee: Hoss Man
> Attachments: SOLR-5463__straw_man.patch, SOLR-5463__straw_man.patch,
> SOLR-5463__straw_man.patch, SOLR-5463__straw_man.patch,
> SOLR-5463__straw_man.patch, SOLR-5463__straw_man.patch,
> SOLR-5463__straw_man.patch, SOLR-5463__straw_man.patch,
> SOLR-5463__straw_man.patch
>
>
> I'd like to revist a solution to the problem of "deep paging" in Solr,
> leveraging an HTTP based API similar to how IndexSearcher.searchAfter works
> at the lucene level: require the clients to provide back a token indicating
> the sort values of the last document seen on the previous "page". This is
> similar to the "cursor" model I've seen in several other REST APIs that
> support "pagnation" over a large sets of results (notable the twitter API and
> it's "since_id" param) except that we'll want something that works with
> arbitrary multi-level sort critera that can be either ascending or descending.
> SOLR-1726 laid some initial ground work here and was commited quite a while
> ago, but the key bit of argument parsing to leverage it was commented out due
> to some problems (see comments in that issue). It's also somewhat out of
> date at this point: at the time it was commited, IndexSearcher only supported
> searchAfter for simple scores, not arbitrary field sorts; and the params
> added in SOLR-1726 suffer from this limitation as well.
> ---
> I think it would make sense to start fresh with a new issue with a focus on
> ensuring that we have deep paging which:
> * supports arbitrary field sorts in addition to sorting by score
> * works in distributed mode
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
