Thanks Ashutosh.
Actually for this kind of query, if I put the 2 filters in WHERE clause
instead of ON clause, the query result is correct.
Do you suggest we put all filters into WHERE or OR clause? And Why?
On Wed, Sep 2, 2015 at 3:13 PM, Ashutosh Chauhan
wrote:
> It indeed is. Title of bug is
It indeed is. Title of bug is symptom of problem and
doesn't accurately describe the problem. Bug will be triggered if following
conditions are met:
If query contains 3 or more joins
AND
joins are merged (i.e. tables participating in two of those joins are
joined on same keys)
AND
these merged joi
Hi Ashutosh,
Is Hive-10841 related? from the title of that jira, it sais “where col is
not null”caused the issue; however above reproduce did not have that clause.
On Wed, Sep 2, 2015 at 2:24 AM, Ashutosh Chauhan
wrote:
> https://issues.apache.org/jira/browse/HIVE-10841
>
> Thanks,
> Ashutosh
https://issues.apache.org/jira/browse/HIVE-10841
Thanks,
Ashutosh
On Tue, Sep 1, 2015 at 6:00 PM, Jim Green wrote:
> Seems Hive 1.2 fixed this issue. But not sure what is the JIRA related and
> the possibility to backport this fix into Hive 0.13?
>
>
> On Tue, Sep 1, 2015 at 5:35 PM, Jim Green
Seems Hive 1.2 fixed this issue. But not sure what is the JIRA related and
the possibility to backport this fix into Hive 0.13?
On Tue, Sep 1, 2015 at 5:35 PM, Jim Green wrote:
> Hi Team,
>
> Below is the minimum reproduce of wrong results in Hive 0.13:
>
> *1. Create 4 tables*
> CREATE EXTERNA
Hi Team,
Below is the minimum reproduce of wrong results in Hive 0.13:
*1. Create 4 tables*
CREATE EXTERNAL TABLE testjoin1( joincol string );
CREATE EXTERNAL TABLE testjoin2(
anothercol string ,
joincol string);
CREATE EXTERNAL TABLE testjoin3( anothercol string);
CREATE EXTERNAL TABLE t
