[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878581#action_12878581
]
David Smiley commented on LUCENE-2454:
--------------------------------------
35.7MB of RAM for every filter is a LOT compared to the 357KB I need now
(100x). Presumably the facet intersections now take 100x as long too. I cache
nearly a thousand of these per index (lots of faceting!) which is by the way
just one Solr shard of many. No can do. :-(
I wonder if its plausible to consider a different implementation strategy
employing a parallel index with the child documents storing the document IDs to
the parent index. I might even assume I need no more than 1000 child documents
and thus index blank documents as filler so that if I am looking at a child
document with id 32005 then it is the 6th sub-entity belonging to parent
document id 32. I know that document IDs are a bit transient so I know that
some care would be needed to maintain this strategy. Thoughts?
> Nested Document query support
> -----------------------------
>
> Key: LUCENE-2454
> URL: https://issues.apache.org/jira/browse/LUCENE-2454
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Search
> Affects Versions: 3.0.2
> Reporter: Mark Harwood
> Assignee: Mark Harwood
> Priority: Minor
> Attachments: LuceneNestedDocumentSupport-1.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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
