[
https://issues.apache.org/jira/browse/IMPALA-8999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958579#comment-16958579
]
ASF subversion and git services commented on IMPALA-8999:
---------------------------------------------------------
Commit b02f51458396e5d9fcb1444ae9d33642cbf9580f in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=b02f514 ]
IMPALA-8999: make union scheduling work with mt_dop
This change unifies mt_dop scheduling between the
union and scan cases.
Testing:
Manually checked that fragments with unions get parallelised
to the correct degree, both as a result of scans within the
fragment and input fragments.
Extend TestMtDopAdmissionSlots (renamed to TestMtDopScheduling)
to confirm that queries that were not parallelised before are
now parallelised. These tests verify the number of instances
of each operator using the ExecSummary embedded in the profile.
Change-Id: I0d2e9c86b530da3053e49d42b837dca0b1348ff2
Reviewed-on: http://gerrit.cloudera.org:8080/14384
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Parallelise all plans, including UNION, when mt_dop > 1
> -------------------------------------------------------
>
> Key: IMPALA-8999
> URL: https://issues.apache.org/jira/browse/IMPALA-8999
> Project: IMPALA
> Issue Type: Sub-task
> Components: Distributed Exec
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
>
> We should do another pass over the scheduler to make sure that the logic
> makes sense for mt_dop.
> There are some comments in scheduler.cc, e.g. talking about optimisations for
> UNION.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
