[
https://issues.apache.org/jira/browse/IMPALA-9586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282136#comment-17282136
]
ASF subversion and git services commented on IMPALA-9586:
---------------------------------------------------------
Commit 8551805875fcd2c701d988df887c1173520fca12 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=8551805 ]
IMPALA-9586: update query option docs for mt_dop
There are interactions between mt_dop and num_nodes and
num_scanner_threads. Mention these in the docs.
Change-Id: I3d9a6f56ffaf211d7d3ca1fad506ee83d516ccbd
Reviewed-on: http://gerrit.cloudera.org:8080/17043
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Joe McDonnell <[email protected]>
> Update query option docs to account for interactions with mt_dop
> ----------------------------------------------------------------
>
> Key: IMPALA-9586
> URL: https://issues.apache.org/jira/browse/IMPALA-9586
> Project: IMPALA
> Issue Type: Improvement
> Components: Docs
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Fix For: Impala 4.0
>
>
> in some cases mt_dop changes the behaviour of other options or makes them a
> no-op. We need to update docs to reflect this.
> * Setting NUM_NODES=1 along with MT_DOP >=1 effectively reduces MT_DOP to 1,
> i.e. only one thread is used.
> * NUM_SCANNER_THREADS has no effect when MT_DOP>=1
> * Maybe other changes?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
