[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052644#comment-13052644
]
Michael McCandless commented on LUCENE-2454:
--------------------------------------------
bq. A variant of prevSetBit could take this largest known child as an argument
to limit its search,
I think we should not require the app to "know" the max number of children per
parent? (Ie, we should just grow buffers, etc., on demand as we collect).
I mean, if this information is easily available we could optimize for that
case, but for some apps it's a good amount of work to record this and update it
so I don't think it should be a required arg when creating the
query/collectors, even though it's tempting ;)
> Nested Document query support
> -----------------------------
>
> Key: LUCENE-2454
> URL: https://issues.apache.org/jira/browse/LUCENE-2454
> Project: Lucene - Java
> Issue Type: New Feature
> Components: core/search
> Affects Versions: 3.0.2
> Reporter: Mark Harwood
> Assignee: Mark Harwood
> Priority: Minor
> Attachments: LUCENE-2454.patch, LUCENE-2454.patch,
> LuceneNestedDocumentSupport.zip
>
>
> A facility for querying nested documents in a Lucene index as outlined in
> http://www.slideshare.net/MarkHarwood/proposal-for-nested-document-support-in-lucene
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
