Re: Best way to avoid cross join

Stage-1: number of mappers: 3; number of >>>>>> reducers: 1 >>>>>> >>>>>> What could be setup wrong here? Or can it be avoided to use this ugly >>>>>> cross join at all? I mean my original problem is actually something else >>>>>> ;-) >>>>>> &

Re: Best way to avoid cross join

this ugly >>>>> cross join at all? I mean my original problem is actually something else >>>>> ;-) >>>>> >>>>> Cheers >>>>> Wolli >>>>> >>>>> >>>>> 2014-03-05 15

Re: Best way to avoid cross join

lli >>>> >>>> >>>> 2014-03-05 15:07 GMT+01:00 java8964 : >>>> >>>> Hi, Wolli: >>>>> >>>>> Cross join doesn't mean Hive has to use one reduce. >>>>> >>>>> From query po

Re: Best way to avoid cross join

;> From query point of view, the following cases will use one reducer: >>>> >>>> 1) Order by in your query (Instead of using sort by) >>>> 2) Only one reducer group, which means all the data have to send to one >>>> reducer, as there is only one reducer

Re: Best way to avoid cross join

>>> >>> 1) Order by in your query (Instead of using sort by) >>> 2) Only one reducer group, which means all the data have to send to one >>> reducer, as there is only one reducer group. >>> >>> In your case, distinct count of id1 will be the r

RE: Best way to avoid cross join

Sorry, my mistake. I didn't pay attention that you are using cross join. Yes, cross join will always use one reducer, at least that is my understand. Yong Date: Wed, 5 Mar 2014 15:27:48 +0100 Subject: Re: Best way to avoid cross join From: darkwoll...@gmail.com To: user@hive.apache.org hey

Re: Best way to avoid cross join

>> In your case, distinct count of id1 will be the reducer group count. Did >> you explicitly set the reducer count in your hive session? >> >> Yong >> >> -- >> Date: Wed, 5 Mar 2014 14:17:24 +0100 >> Subject: Best way to avoid cross join >> Fr

Re: Best way to avoid cross join

to send to one > reducer, as there is only one reducer group. > > In your case, distinct count of id1 will be the reducer group count. Did > you explicitly set the reducer count in your hive session? > > Yong > > ------ > Date: Wed, 5 Mar 2014

RE: Best way to avoid cross join

reducer group. In your case, distinct count of id1 will be the reducer group count. Did you explicitly set the reducer count in your hive session? Yong Date: Wed, 5 Mar 2014 14:17:24 +0100 Subject: Best way to avoid cross join From: darkwoll...@gmail.com To: user@hive.apache.org Hey everyone,

Best way to avoid cross join

Hey everyone, before i write a lot of text, i just post something which is already written: http://www.sqlservercentral.com/Forums/Topic1328496-360-1.aspx The first posts adresses a pretty similar problem i also have. Currently my implementation looks like this: SELECT id1, MAX( CASE WHE