[
https://issues.apache.org/jira/browse/HIVE-13068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254475#comment-15254475
]
Ashutosh Chauhan commented on HIVE-13068:
-----------------------------------------
Historically latency of doing optimization on Hive tree comes from slowness of
traversing operator & expression tree, not of doing optimization itself
(executing folding logic in this case). So my guess is even if you are
executing very little logic latency of doing walk on trees will outnumber any
gains. So, my assumption is we will see benefit of migration only if we can
totally avoid the optimization on Hive tree. Further, it still leaves the room
for bugs in new code, which is avoidable.
So my suggestion is to instead try to fix all issues which comes out of it,
instead of having this new simplified rule.
> Disable Hive ConstantPropagate optimizer when CBO has optimized the plan II
> ---------------------------------------------------------------------------
>
> Key: HIVE-13068
> URL: https://issues.apache.org/jira/browse/HIVE-13068
> Project: Hive
> Issue Type: Sub-task
> Components: CBO, Logical Optimizer
> Affects Versions: 2.1.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Attachments: HIVE-13068.01.patch, HIVE-13068.01.patch,
> HIVE-13068.patch
>
>
> After HIVE-12543 went in, we need follow-up work to disable the last call to
> ConstantPropagate in Hive. This probably implies work on extending the
> constant folding logic in Calcite.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
