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

Posted to issues@hive.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2023/06/05 11:08:00 UTC

[jira] [Commented] (HIVE-26968) SharedWorkOptimizer merges TableScan operators that have different DPP parents

    [ https://issues.apache.org/jira/browse/HIVE-26968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729279#comment-17729279 ] 

Stamatis Zampetakis commented on HIVE-26968:
--------------------------------------------

[~seonggon] From some tests that I did locally it seems that the value of hive.optimize.shared.work.dppunion is not important to reproduce the problem. With the simplified test that I pushed in #3981 I get wrong results consistently for both dppunion=true and dppunion=false.

> SharedWorkOptimizer merges TableScan operators that have different DPP parents
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-26968
>                 URL: https://issues.apache.org/jira/browse/HIVE-26968
>             Project: Hive
>          Issue Type: Sub-task
>    Affects Versions: 4.0.0-alpha-2
>            Reporter: Seonggon Namgung
>            Assignee: Seonggon Namgung
>            Priority: Critical
>              Labels: hive-4.0.0-must, pull-request-available
>         Attachments: TPC-DS Query64 OperatorGraph.pdf
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> SharedWorkOptimizer merges TableScan operators that have different DPP parents, which leads to the creation of semantically wrong query plan.
> In our environment, running TPC-DS query64 on 1TB Iceberg format table returns no rows  because of this problem. (The correct result has 7094 rows.)
> We use hive.optimize.shared.work=true, hive.optimize.shared.work.extended=true, and hive.optimize.shared.work.dppunion=false to reproduce the bug.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)