[
https://issues.apache.org/jira/browse/HIVE-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912845#action_12912845
]
Namit Jain commented on HIVE-1534:
----------------------------------
What I meant to say was the following:
People are running queries in the warehouse with the expected wrong semantics -
if we suddenly fix this, the queries will break.
We need to give some time to everyone to change their queries to use a
sub-query if they want the filter to be pushed up.
Adding the above config, parameter seems like the only choice - we can try to
remove this parameter before 0.7 goes out
(if everyone agrees), but we need it right now for deployment
> Join filters do not work correctly with outer joins
> ---------------------------------------------------
>
> Key: HIVE-1534
> URL: https://issues.apache.org/jira/browse/HIVE-1534
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Attachments: patch-1534-1.txt, patch-1534-2.txt, patch-1534-3.txt,
> patch-1534.txt
>
>
> SELECT * FROM T1 LEFT OUTER JOIN T2 ON (T1.c1=T2.c2 AND T1.c1 < 10)
> and SELECT * FROM T1 RIGHT OUTER JOIN T2 ON (T1.c1=T2.c2 AND T2.c1 < 10)
> do not give correct results.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.