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

ASF subversion and git services commented on IMPALA-12444:
----------------------------------------------------------

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]>


> PROCESSING_COST_MIN_THREADS can get ignored by scan fragment.
> -------------------------------------------------------------
>
>                 Key: IMPALA-12444
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12444
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 4.2.0
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> There is a bug in PlanFragment.java where scan fragment might not follow 
> PROCESSING_COST_MIN_THREADS set by user even if total scan ranges allow to do 
> so.
> Frontend planner also need to sanity check such that 
> PROCESSING_COST_MIN_THREADS <= MAX_FRAGMENT_INSTANCES_PER_NODE.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to