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

2017-02-13 Thread Eugene Koifman (JIRA)

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

Eugene Koifman updated HIVE-15839:
--
   Resolution: Fixed
Fix Version/s: 2.2.0
   Status: Resolved  (was: Patch Available)

HIVE-15839.03.patch committed to master
thanks Wei for the review

> 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
> Fix For: 2.2.0
>
> Attachments: HIVE-15839.01.patch, HIVE-15839.02.patch, 
> HIVE-15839.03.patch
>
>
> 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)


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

2017-02-10 Thread Eugene Koifman (JIRA)

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

Eugene Koifman updated HIVE-15839:
--
Status: Patch Available  (was: Open)

> 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
> Attachments: HIVE-15839.01.patch, HIVE-15839.02.patch, 
> HIVE-15839.03.patch
>
>
> 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)


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

2017-02-10 Thread Eugene Koifman (JIRA)

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

Eugene Koifman updated HIVE-15839:
--
Attachment: HIVE-15839.03.patch

> 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
> Attachments: HIVE-15839.01.patch, HIVE-15839.02.patch, 
> HIVE-15839.03.patch
>
>
> 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)


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

2017-02-10 Thread Eugene Koifman (JIRA)

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

Eugene Koifman updated HIVE-15839:
--
Status: Open  (was: Patch Available)

> 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
> Attachments: HIVE-15839.01.patch, HIVE-15839.02.patch
>
>
> 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)


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

2017-02-10 Thread Eugene Koifman (JIRA)

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

Eugene Koifman updated HIVE-15839:
--
Status: Patch Available  (was: Open)

> 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
> Attachments: HIVE-15839.01.patch
>
>
> 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)


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

2017-02-10 Thread Eugene Koifman (JIRA)

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

Eugene Koifman updated HIVE-15839:
--
Attachment: HIVE-15839.02.patch

> 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
> Attachments: HIVE-15839.01.patch, HIVE-15839.02.patch
>
>
> 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)


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

2017-02-09 Thread Eugene Koifman (JIRA)

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

Eugene Koifman updated HIVE-15839:
--
Attachment: HIVE-15839.01.patch

> 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
>Priority: Minor
> Attachments: HIVE-15839.01.patch
>
>
> 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)


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

2017-02-07 Thread Eugene Koifman (JIRA)

 [ 
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)