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

Posted to issues@hive.apache.org by "Sungwoo Park (Jira)" <ji...@apache.org> on 2023/01/25 10:13: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=17680530#comment-17680530 ] 

Sungwoo Park commented on HIVE-26968:
-------------------------------------

Considering the fact that shared work optimizer (with the default value of hive.optimize.shared.work.extended=true) is extensively used, I suggest that the priority should be set to critical.

> 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: Bug
>    Affects Versions: 4.0.0-alpha-2
>            Reporter: Seonggon Namgung
>            Assignee: Seonggon Namgung
>            Priority: Critical
>              Labels: pull-request-available
>          Time Spent: 20m
>  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)