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

Phil Phillips edited comment on SOLR-7090 at 11/18/16 11:42 PM:
----------------------------------------------------------------

The "fulljoin" patch seems to do the trick for me.  One thing I noticed is that 
in the facet query, I had to add {{facet.limit=-1}} to get it to return all the 
results (this was for a larger index). So far, it's performing reasonably well. 
I can report back once I add in more documents.

As Erick suggested, I did try streaming as well. I was able to get what I 
wanted with a stream expression (with {{sort}} and {{innerJoin}}).  However, I 
could only get it to work the way I wanted if I stored the fields that I was 
joining/sorting on. That wouldn't be ideal in my scenario.


was (Author: irphilli):
The "fulljoin" patch seems to do the trick for me.  One thing I noticed is that 
in the facet query, I had to add {{facet.limit=-1}} to get it to return all the 
results (this was for a larger index). So far, it's performing reasonably well. 
I can report back once I add in more documents.

As Erick suggested, I did try a streaming as well. I was able to get what I 
wanted with a stream expression (with {{sort}} and {{innerJoin}}).  However, I 
could only get it to work the way I wanted if I stored the fields that I was 
joining/sorting on. That wouldn't be ideal in my scenario.

> Cross collection join
> ---------------------
>
>                 Key: SOLR-7090
>                 URL: https://issues.apache.org/jira/browse/SOLR-7090
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Ishan Chattopadhyaya
>             Fix For: 5.2, 6.0
>
>         Attachments: SOLR-7090-fulljoin.patch, SOLR-7090.patch
>
>
> Although SOLR-4905 supports joins across collections in Cloud mode, there are 
> limitations, (i) the secondary collection must be replicated at each node 
> where the primary collection has a replica, (ii) the secondary collection 
> must be singly sharded.
> This issue explores ideas/possibilities of cross collection joins, even 
> across nodes. This will be helpful for users who wish to maintain boosts or 
> signals in a secondary, more frequently updated collection, and perform query 
> time join of these boosts/signals with results from the primary collection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to