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/01/17 23:09:26 UTC
[jira] [Resolved] (HIVE-14946) Optimizations
[ https://issues.apache.org/jira/browse/HIVE-14946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eugene Koifman resolved HIVE-14946.
-----------------------------------
Resolution: Duplicate
Fix Version/s: 2.2.0
addressed by HIVE-15539
> Optimizations
> -------------
>
> Key: HIVE-14946
> URL: https://issues.apache.org/jira/browse/HIVE-14946
> Project: Hive
> Issue Type: Sub-task
> Components: Query Planning, Transactions
> Reporter: Eugene Koifman
> Assignee: Eugene Koifman
> Fix For: 2.2.0
>
>
> For example, if there is only WHEN NOT MATCHED clause, the base generating expression can be an INNER JOIN
> Generally, we should make sure the optimizer is able to work with the plan for Merge statement
> Various WHEN clauses can have "extra" predicates. In some cases they may be pushable.
> The "source" can be an arbitrary expression - in particular it may include joins which together with the join introduced by Merge itself may need to be reordered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)