Yes, joins support distributed search fine,
provided that the individual documents that are joined reside on the same shard.
For example, if you are modeling blogs and posts (one blog object as many posts)
shard1
------------------
joe!blog_info
joe!post1
shard2
------------------
mary!blog_info
mary!post1
So now you can search for post bodies and join to the main blog via
{!join from=blog_pointer to=blog_id}post_body:hello
If both mary and joe have a post with hello, they will both be found
and joined to their main blog info docs with a single distributed
search across the collection.
-Yonik
http://lucidworks.com
On Thu, Jul 4, 2013 at 3:37 AM, slevytam <[email protected]> wrote:
> Hi Yonik,
>
> Thanks for the reply. It was very helpful.
>
> This may be a newb question but will this work on a individual rows of a
> query or do all the queries' results need to be on the same shard.
>
> ex.
>
> if the main query would return
> - user15 (shard 1)
> - user16 (shard 2)
> - user17 (shard 3)
>
> is it acceptable to have
> doc1 (shard 1)
> whatever (shard 2)
> yeah (shard 3)
>
> for a join of
> - user15, doc1
> - user16, whatever
> - user17, yeah
>
> or do all the results of the main query need to reside on the same shard as
> all the results of join.
>
> Hopefully that's an understandable question.
>
> Thanks,
>
> slevytam
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Joins-with-SolrCloud-tp4073199p4075408.html
> Sent from the Solr - User mailing list archive at Nabble.com.