[
https://issues.apache.org/jira/browse/IMPALA-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238510#comment-17238510
]
ASF subversion and git services commented on IMPALA-10351:
----------------------------------------------------------
Commit c4e7977f5ee1b740215eb486a074bc1326cff360 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=c4e7977 ]
IMPALA-10351,IMPALA-9812: enable mt_dop for DML by default
This allows setting mt_dop for any query with any configuration.
Before this patch it was not supported for DML.
--unlock_mt_dop and --mt_dop_auto_fallback are now ignored.
Testing:
* Updated tests to reflect new behaviour.
* Removed irrelevant tests for fallback/validation.
* Ran exhaustive tests.
Change-Id: I66331481260fe4b69d9e95b0200029b14d230ade
Reviewed-on: http://gerrit.cloudera.org:8080/16775
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[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
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
