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

Posted to issues-all@impala.apache.org by "Riza Suminto (Jira)" <ji...@apache.org> on 2023/04/26 21:10:00 UTC

[jira] [Commented] (IMPALA-12091) Control scan fragment parallelism by its processing cost

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

Riza Suminto commented on IMPALA-12091:
---------------------------------------

Filed a gerrit review here: https://gerrit.cloudera.org/c/19807/

> Control scan fragment parallelism by its processing cost
> --------------------------------------------------------
>
>                 Key: IMPALA-12091
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12091
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: Impala 4.2.0
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Major
>
> Impala still rely on MT_DOP option to decide parallelism of scan fragment when query runs with COMPUTE_PROCESSING_COST=1. Planner should decide scan parallelism by its processing cost instead of fixed count dictated by MT_DOP.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org