You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "mahesh kumar behera (Jira)" <ji...@apache.org> on 2020/08/07 05:05:00 UTC

[jira] [Updated] (HIVE-24013) Move anti join conversion after join reordering rule

     [ https://issues.apache.org/jira/browse/HIVE-24013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mahesh kumar behera updated HIVE-24013:
---------------------------------------
    Description: The current anti join conversion is done before join re-ordering rule. As Anti join is not handled in join re-ordering, it is better to move the anti join conversion after join reordering is done.  (was: The current anti join conversion does not check for null filters on right side of join if it's within OR conditions. Only those filters separated by AND conditions are supported. For example queries like "select t1.fld from tbl1 t1 left join tbl2 t2 on t1.fld = t2.fld where t2.fld is null or t2.fld1 is null" are not converted to anti join. )

> Move anti join conversion after join reordering rule
> ----------------------------------------------------
>
>                 Key: HIVE-24013
>                 URL: https://issues.apache.org/jira/browse/HIVE-24013
>             Project: Hive
>          Issue Type: Bug
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>
> The current anti join conversion is done before join re-ordering rule. As Anti join is not handled in join re-ordering, it is better to move the anti join conversion after join reordering is done.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)