[
https://issues.apache.org/jira/browse/IMPALA-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778930#comment-17778930
]
ASF subversion and git services commented on IMPALA-12510:
----------------------------------------------------------
Commit 1388be8eb8011eaad45327e2da8671a1ff10844e in impala's branch
refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=1388be8eb ]
IMPALA-12510: Floor PlanFragment.maxParallelism_ at 1
IMPALA-12444 introduce a bug where PlanFragment.maxParallelism_ can be
set to 0. This can happen at scan fragment if table is empty. Number of
scan ranges will be 0, which then propagate to
ScanNode.maxScannerThreads_ and PlanFragment.maxParallelism_.
This patch fix it by flooring ScanNode.maxScannerThreads_ and
PlanFragment.maxParallelism_ at 1.
Testing:
- Add select star over an empty table testcase to
PlannerTest.testProcessingCost.
Change-Id: Ibfa50abfdb9cdb994c5c3d7904b377a25f5b8b97
Reviewed-on: http://gerrit.cloudera.org:8080/20606
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Riza Suminto <[email protected]>
> 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: [email protected]
For additional commands, e-mail: [email protected]
