You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Martijn van Groningen (JIRA)" <ji...@apache.org> on 2012/05/07 22:20:48 UTC

[jira] [Issue Comment Edited] (LUCENE-3938) Add query time parent child search

    [ https://issues.apache.org/jira/browse/LUCENE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269970#comment-13269970 ] 

Martijn van Groningen edited comment on LUCENE-3938 at 5/7/12 8:20 PM:
-----------------------------------------------------------------------

Updated patch. 
* Added simple test case that shows a simple use case. 
* Removed groupParent and groupChild in favor of disAllowHitsFromTheSameRelation in ParentChildCommand class.
                
      was (Author: martijn.v.groningen):
    Updated patch. 
* Added simple test case that shows a simple use case. 
* Removed groupParent and groupChildren in favor of disAllowHitsFromTheSameRelation in ParentChildCommand class.
                  
> Add query time parent child search
> ----------------------------------
>
>                 Key: LUCENE-3938
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3938
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: modules/join
>            Reporter: Martijn van Groningen
>         Attachments: LUCENE-3938.patch, LUCENE-3938.patch
>
>
> At the moment there is support for index time parent child search with two queries implementations and a collector. The index time parent child search requires that documents are indexed in a block, this isn't ideal for updatability. For example in the case of tv content and subtitles (both being separate documents). Updating already indexed tv content with subtitles would then require to also re-index the subtitles.
> This issue focuses on the collector part for query time parent child search. I started a while back with implementing this. Basically a two pass search performs a parent child search. In the first pass the top N parent child documents are resolved. In the second pass the parent or top N children are resolved (depending if the hit is a parent or child) and are associated with the top N parent child relation documents. Patch will follow soon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org