lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3076) Solr should support block joins
Date Thu, 09 Feb 2012 23:10:58 GMT


Michael McCandless commented on SOLR-3076:

Mikhail, I think something like that looks right?  It expresses the join structure to the

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:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message