e excuse typos
>
> -Original Message-
> From: "David Morel"
> Date: Thu, 24 Jan 2013 18:39:56
> To: ;
> Reply-To: user@hive.apache.org
> Subject: Re: An explanation of LEFT OUTER JOIN and NULL values
>
> On 24 Jan 2013, at 18:16, bejoy...@yahoo.com wr
-Original Message-
From: "David Morel"
Date: Thu, 24 Jan 2013 18:39:56
To: ;
Reply-To: user@hive.apache.org
Subject: Re: An explanation of LEFT OUTER JOIN and NULL values
On 24 Jan 2013, at 18:16, bejoy...@yahoo.com wrote:
> Hi David
>
> An explain extended would
Regards
> Bejoy KS
>
> Sent from remote device, Please excuse typos
>
> -Original Message-
> From: "David Morel"
> Date: Thu, 24 Jan 2013 18:03:40
> To: user@hive.apache.org
> Reply-To: user@hive.apache.org
> Subject: An explanation of LEFT OUTER JOIN and NULL va
4 Jan 2013 18:03:40
To: user@hive.apache.org
Reply-To: user@hive.apache.org
Subject: An explanation of LEFT OUTER JOIN and NULL values
Hi!
After hitting the "curse of the last reducer" many times on LEFT OUTER
JOIN queries, and trying to think about it, I came to the conclusion
th
Hi!
After hitting the "curse of the last reducer" many times on LEFT OUTER
JOIN queries, and trying to think about it, I came to the conclusion
there's something I am missing regarding how keys are handled in mapred
jobs.
The problem shows when I have table A containing billions of rows with
dist
