[
https://issues.apache.org/jira/browse/SOLR-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205016#comment-13205016
]
Michael McCandless commented on SOLR-3076:
------------------------------------------
Mikhail, I think something like that looks right? It expresses the join
structure to the QP.
Hoss, you're right, you can have the same field name on
parent/child/grandchild/etc., so I agree, we will need something in the query
syntax to disambiguate which is which for such cases. Though I would think
this would be the exception not the rule (ie, I'd expect apps to name the
fields "uniquely" across parent and child docs).
Maybe there can be field aliases? Eg, book_page_count:[0 to 1000] and
chapter_page_count[10:40], and the QP is told to map book_page_count ->
parent:size and chapter_page_count -> child:size? Or maybe we let the user
explicitly scope the field, eg chapter:size, book:size, book:title, etc. Not
sure...
> Solr should support block joins
> -------------------------------
>
> Key: SOLR-3076
> URL: https://issues.apache.org/jira/browse/SOLR-3076
> Project: Solr
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Attachments: SOLR-3076.patch, bjq-vs-filters-backward-disi.patch,
> bjq-vs-filters-illegal-state.patch, parent-bjq-qparser.patch,
> parent-bjq-qparser.patch, solrconf-bjq-erschema-snippet.xml
>
>
> Lucene has the ability to do block joins, we should add it to Solr.
--
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: [email protected]
For additional commands, e-mail: [email protected]
