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/07/24 03:52:00 UTC

[jira] [Updated] (HIVE-23920) Need to handle HiveJoinConstraintsRule for Anti Join

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

mahesh kumar behera updated HIVE-23920:
---------------------------------------
    Description: 
 If we have a PK-FK join that is only appending columns to the FK side, it basically means it is not filtering anything (everything is matching). If that is the case, then ANTIJOIN result would be empty. We could detect this at planning time and trigger the rewriting.

 

  was:
Currently in Hive we create different operator for different kind of join. n Calcite, it all seems to be based on a single Join class in newer releases. So the classes like HiveAntiJoin, HiveSemiJoin can be merged into one.

 


> Need to handle HiveJoinConstraintsRule for Anti Join
> ----------------------------------------------------
>
>                 Key: HIVE-23920
>                 URL: https://issues.apache.org/jira/browse/HIVE-23920
>             Project: Hive
>          Issue Type: Bug
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>
>  If we have a PK-FK join that is only appending columns to the FK side, it basically means it is not filtering anything (everything is matching). If that is the case, then ANTIJOIN result would be empty. We could detect this at planning time and trigger the rewriting.
>  



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