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/10/20 18:52:00 UTC
[jira] [Commented] (IMPALA-12510) ProcessingCost.getNumInstanceMax() should not return 0.
[ https://issues.apache.org/jira/browse/IMPALA-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777913#comment-17777913 ]
Riza Suminto commented on IMPALA-12510:
---------------------------------------
The issue happen when running query with COMPUTE_PROCESSING_COST=1 over empty table.
Digging some more, looks like the true culprit is here where it does min without flooring it at 1:
[https://github.com/apache/impala/blob/b15d6dc2e7df05392a1daa4bc1b3da9ca31a583b/fe/src/main/java/org/apache/impala/planner/PlanFragment.java#L1139]
> ProcessingCost.getNumInstanceMax() should not return 0.
> -------------------------------------------------------
>
> Key: IMPALA-12510
> URL: https://issues.apache.org/jira/browse/IMPALA-12510
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 4.3.0
> Reporter: Riza Suminto
> Assignee: Riza Suminto
> Priority: Major
>
> ProcessingCost.getNumInstanceMax() is used for calculating cost-based max parallelism. It should return 1 at minimum, not 0.
> [https://github.com/apache/impala/blob/b15d6dc2e7df05392a1daa4bc1b3da9ca31a583b/fe/src/main/java/org/apache/impala/planner/ProcessingCost.java#L207-L211]
--
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