[
https://issues.apache.org/jira/browse/HIVE-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912425#action_12912425
]
Amareshwari Sriramadasu commented on HIVE-1657:
-----------------------------------------------
Here is a usecase:
{noformat}
hive> select * from table1;
12 35
NULL 36
48 40
40 40
NULL 45
100 100
hive> select * from myinput1;
12 35
NULL 40
48 NULL
100 100
hive> SELECT * from table1 a RIGHT OUTER JOIN myinput1 b ON (a.value=b.value)
LEFT OUTER JOIN table1 c ON (b.key=c.key);
NULL 40 48 40 NULL NULL
NULL 40 40 40 NULL NULL
12 35 12 35 12 35
48 NULL NULL NULL 48 40
100 100 100 100 100 100
{noformat}
> join results are displayed wrongly for some complex joins
> ---------------------------------------------------------
>
> Key: HIVE-1657
> URL: https://issues.apache.org/jira/browse/HIVE-1657
> Project: Hadoop Hive
> Issue Type: Bug
> Reporter: Amareshwari Sriramadasu
>
> Noticed that the output of the join is displayed wrongly for queries
> involving more than one table and mixture of left and outer joins, with
> different join conditions.
> For ex: SELECT * from T1 a RIGHT OUTER JOIN T2 b ON (a.value=b.value) LEFT
> OUTER JOIN T3 c ON (b.key=c.key);
> displays the table T2 first, then T1 and T3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
