[
https://issues.apache.org/jira/browse/SOLR-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222958#comment-17222958
]
Bar Rotstein commented on SOLR-14963:
-------------------------------------
+1 to no limit by default.
I think in the dev forum the proposal was to limit the immediate children:
bq. So, is that (all nested children included in limit) what we actually mean?
Or did we mean maximum number of "immediate children" for any specific
document/level and the code is wrong?`
IMO, this makes a little more sense than the current logic.
WDYT?
> Child "rows" param should apply per level
> -----------------------------------------
>
> Key: SOLR-14963
> URL: https://issues.apache.org/jira/browse/SOLR-14963
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Priority: Major
>
> The {{[child rows=10]}} doc transformer "rows" param _should_ apply per
> parent, and it's documented this way: "The maximum number of child documents
> to be returned per parent document.". However, it is instead implemented as
> an overall limit as the child documents are processed in a depth-first order
> way. The implementation ought to change.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
