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

Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2017/02/07 19:51:41 UTC

[jira] [Updated] (HIVE-15839) Don't force cardinality check if only WHEN NOT MATCHED is specified

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

Eugene Koifman updated HIVE-15839:
----------------------------------
    Priority: Minor  (was: Major)

> Don't force cardinality check if only WHEN NOT MATCHED is specified
> -------------------------------------------------------------------
>
>                 Key: HIVE-15839
>                 URL: https://issues.apache.org/jira/browse/HIVE-15839
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Query Planning, Query Processor, Transactions
>    Affects Versions: 2.2.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Minor
>
> should've been part of HIVE-14949
> if only WHEN NOT MATCHED is specified then the join is basically an anti-join and we are not retrieving any values from target side. So the cardinality check is just overhead (though presumably very minor since the filter above the join will filter everything and thus there is nothing to group)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)