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

Jonathan Rochkind commented on SOLR-2272:
-----------------------------------------

Even if the core's aren't in the same JVM, one could imagine a weird 
cross-host join where Solr actually connected to the external Solr, 
issued a query (perhaps using Solr binary format for efficiency, SolrJ 
style), got the list of values returned for a particular stored field, 
and used that as a filter on the current query.

This is in fact similar to something that's come up (not sure if it's in 
a different ticket or just on listserv) about doing a similar thing with 
an external SQL query, where the result of some single-column SQL 
against an external database is used as a filter in the current query.  
Really the exact same problem, just a question of whether the external 
query is to SQL via JDBC or what have you, or instead to another core 
via SolrJ style connection.  Either way do an external query, end up 
with a list of values, and want to use that as efficiently as possible 
(ie, NOT using lucene 'or' with hundreds or thousands of clauses!) as a 
filter on a particular solr indexed field for the current query.

But clearly that enhancement would be a different ticket/patch -- if the 
'join' patch as currently spec'd were to make it into Solr as is (same 
core join only) I'd be overjoyed, it would be awfully useful just as it 
is, so do not suggest that it's scope be increased thus raising the bar 
for the feature as is.



> Join
> ----
>
>                 Key: SOLR-2272
>                 URL: https://issues.apache.org/jira/browse/SOLR-2272
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>            Reporter: Yonik Seeley
>             Fix For: 4.0
>
>         Attachments: SOLR-2272.patch, SOLR-2272.patch
>
>
> Limited join functionality for Solr, mapping one set of IDs matching a query 
> to another set of IDs, based on the indexed tokens of the fields.
> Example:
> fq={!join  from=parent_ptr to:parent_id}child_doc:query

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to