You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2014/05/02 18:08:18 UTC

[jira] [Updated] (SOLR-5285) Solr response format should support child Docs

     [ https://issues.apache.org/jira/browse/SOLR-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Varun Thacker updated SOLR-5285:
--------------------------------

    Attachment: SOLR-5285.patch

Updated patch with trunk.

bq. it's not clear to me from the API what to expect will happen if i have more then one level of parent-child relationships in my index – will children & grandchildren be returned? whatever is expected needs to be documented/tested

Tested with grandchildren. In Lucene all grandchildren and all siblings  are treated as simply children to the parent document. A parent document and all it's child documents are indexed in a block. Hence we should document for only support one level of nesting.

> Solr response format should support child Docs
> ----------------------------------------------
>
>                 Key: SOLR-5285
>                 URL: https://issues.apache.org/jira/browse/SOLR-5285
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Varun Thacker
>             Fix For: 4.9, 5.0
>
>         Attachments: SOLR-5285.patch, SOLR-5285.patch, SOLR-5285.patch, SOLR-5285.patch
>
>
> Solr has added support for taking childDocs as input ( only XML till now ). It's currently used for BlockJoinQuery. 
> I feel that if a user indexes a document with child docs, even if he isn't using the BJQ features and is just searching which results in a hit on the parentDoc, it's childDocs should be returned in the response format.
> [~hossman_lucene@fucit.org] on IRC suggested that the DocTransformers would be the place to add childDocs to the response.
> Now given a docId one needs to find out all the childDoc id's. A couple of approaches which I could think of are 
> 1. Maintain the relation between a parentDoc and it's childDocs during indexing time in maybe a separate index?
> 2. Somehow emulate what happens in ToParentBlockJoinQuery.nextDoc() - Given a parentDoc it finds out all the childDocs but this requires a childScorer.
> Am I missing something obvious on how to find the relation between a parentDoc and it's childDocs because none of the above solutions for this look right.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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