[
https://issues.apache.org/jira/browse/SOLR-12937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668084#comment-16668084
]
Gus Heck commented on SOLR-12937:
---------------------------------
I would guess that the start parameter should handle the top level, and what
you get is a cursor at the top level. This semantic parallels grouping queries
(though I haven't checked how cursors work there!). It sounds like the goal is
to alleviate deep paging. Controlling total return size in the event of many
child docs is perhaps a related problem, but maybe that doesn't have to be
solved at the same time. I haven't looked at how this transformer works, but if
the top level is fetched first and subsequent levels flushed out from there, a
cursor on the top level sounds like it might keep that initial fetch small.
> ChildDocTransformer should have sort and start param
> ----------------------------------------------------
>
> Key: SOLR-12937
> URL: https://issues.apache.org/jira/browse/SOLR-12937
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: mosh
> Priority: Major
>
> Users should be able to pass sort and start params to ChildDocTransformer so
> they can use cursors for nested queries.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
