You can also do the innerJoin in parallel across worker nodes using the
parallel function:
hashJoin(
parallel(workerCollection,
innerJoin(
search(users, q="*:*",
fl="userId, full_name, hometown", sort="userId a
Something I forgot to mention - the collection shards can live on any
number of machines, anywhere in the world. As long as the clusterstate in
zk knows where the shard can be found (ie, a basis of SolrCloud) then
everything will work. The example I gave had the shards living on the same
machine bu
Mugeesh,
You can use Streaming Aggregation to provide various types of
cross-collection joins. This is currently available in trunk and will be a
part of Solr 6.
To follow with your example, let's assume the following setup:
Restaurants: avail on machine1:8983 with 3 shards, zk at zk1:2345
Users:
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
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 a
On Wed, Jul 3, 2013 at 5:40 PM, slevytam wrote:
> Hi Yonik,
>
> Can you offer any insight as to how one might ensure that documents reside
> on the same shard as the document you'd like them to join.
>
> For example:
> I'd like to do a simple join of user actions to a specific document. So, i
> w
Hi Yonik,
Can you offer any insight as to how one might ensure that documents reside
on the same shard as the document you'd like them to join.
For example:
I'd like to do a simple join of user actions to a specific document. So, i
would query for a list of documents and have the user actions on
On Tue, Jun 25, 2013 at 7:55 PM, Upayavira wrote:
> However, if from your example, innerCollection was replicated across all
> nodes, I would think that should work, because all that comes back from
> each server when a distributed search happens is the best 'n' matches,
> so exactly how those 'n'
Thanks, confirmed by trying w/ 4.3.1 that the join works with the outer
collection distributed/sharded so long as the inner collection is not
distributed/sharded.
Chris
On Tue, Jun 25, 2013 at 4:55 PM, Upayavira wrote:
> I have never heard mention that joins support distributed search, so you
IRA above
-- James
-Original Message-
From: Upayavira [mailto:u...@odoko.co.uk]
Sent: Tuesday, June 25, 2013 7:55 PM
To: solr-user@lucene.apache.org
Subject: Re: Joins with SolrCloud
I have never heard mention that joins support distributed search, so you cannot
do a join against a sharded core.
H
I have never heard mention that joins support distributed search, so you
cannot do a join against a sharded core.
However, if from your example, innerCollection was replicated across all
nodes, I would think that should work, because all that comes back from
each server when a distributed search h
11 matches
Mail list logo
