[
https://issues.apache.org/jira/browse/IMPALA-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884794#comment-17884794
]
ASF subversion and git services commented on IMPALA-10351:
----------------------------------------------------------
Commit bcba81a1ded82cd010a9383cf4addbc6b223ef5b in impala's branch
refs/heads/master from Noemi Pap-Takacs
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=bcba81a1d ]
IMPALA-11663: Update documentation for MT_DOP
The MT_DOP documentation was outdated stating that MT_DOP values
greater than zero are not supported for DML statements.
However, IMPALA-10351 introduced this feature and now DML statements
do not produce an error if MT_DOP is set to a non-zero value.
Change-Id: Id34ccdaa8e1738756f4f12f7074e9f076b9209b4
Reviewed-on: http://gerrit.cloudera.org:8080/21846
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Daniel Becker <[email protected]>
> Enable mt_dop for DML
> ---------------------
>
> Key: IMPALA-10351
> URL: https://issues.apache.org/jira/browse/IMPALA-10351
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: multithreading
> Fix For: Impala 4.0.0
>
>
> We don't have any pending issues for MT_DOP with DML and have sufficient
> functional testing, so I think we can go ahead and enable it. IMPALA-8125 and
> query hints give us a safety valve in case we overparallelize.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
