[
https://issues.apache.org/jira/browse/HIVE-23298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098739#comment-17098739
]
Zoltan Haindrich commented on HIVE-23298:
-----------------------------------------
I've just run into some small conflicts relating to this changeset - and I was
looking into the diff; and something have caught my eye:
In
[correlationoptimizer14.q.out|https://github.com/apache/hive/commit/87fc75424d37025fca358a4bc57c5e72a32941fb#diff-16ac21a9d9aedb5a9ade75adb2454968R1184]
the plan have started using bloom filters/etc - however I don't think stat
estimates or anything have changed which should have caused it.
I don't think it's a major issue - but might worth a look.
> Disable RS deduplication step in Optimizer if it is run in TezCompiler
> ----------------------------------------------------------------------
>
> Key: HIVE-23298
> URL: https://issues.apache.org/jira/browse/HIVE-23298
> Project: Hive
> Issue Type: Improvement
> Components: Physical Optimizer
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-23298.1.patch, HIVE-23298.2.patch,
> HIVE-23298.3.patch, HIVE-23298.patch
>
>
> HIVE-20703 introduced an additional RS deduplication step in TezCompiler. We
> could possibly try to disable the one that runs in {{Optimizer}} if we are
> using Tez so we do not run the optimization twice.
> This issue is to explore that possibility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
