[ 
https://issues.apache.org/jira/browse/HIVE-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913221#action_12913221
 ] 

John Sichi commented on HIVE-1657:
----------------------------------

I've confirmed this as a bug by comparing the behavior with MySQL.

{noformat}
mysql> select * from table1;
+------+------+
| k    | v    |
+------+------+
|   12 |   35 | 
| NULL |   36 | 
|   48 |   40 | 
|   40 |   40 | 
| NULL |   45 | 
|  100 |  100 | 
+------+------+
6 rows in set (0.00 sec)

mysql> select * from myinput1;
+------+------+
| k    | v    |
+------+------+
|   12 |   35 | 
| NULL |   40 | 
|   48 | NULL | 
|  100 |  100 | 
+------+------+
4 rows in set (0.00 sec)

mysql> select * from table1 a right outer join myinput1 b on (a.v=b.v) left 
outer join table1 c on (b.k=c.k);
+------+------+------+------+------+------+
| k    | v    | k    | v    | k    | v    |
+------+------+------+------+------+------+
|   12 |   35 |   12 |   35 |   12 |   35 | 
|   48 |   40 | NULL |   40 | NULL | NULL | 
|   40 |   40 | NULL |   40 | NULL | NULL | 
| NULL | NULL |   48 | NULL |   48 |   40 | 
|  100 |  100 |  100 |  100 |  100 |  100 | 
+------+------+------+------+------+------+
5 rows in set (0.00 sec)
{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.

Reply via email to