[
https://issues.apache.org/jira/browse/HIVE-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gunther Hagleitner updated HIVE-8042:
-------------------------------------
Description: hive.exec.parallel allows one to run different stages of a
query in parallel. However that applies only to map-reduce tasks. When using
large multi insert queries there are many MoveTasks that are all executed in
sequence on the client. There's no real reason for that - they could be run in
parallel as well (i.e.: the stage graph captures the dependencies and knows
which tasks can happen in parallel). (was: hive.exec.parallel allows one to
run different stages of a query in parallel. However that applies only to
map-reduce tasks. When using large multi insert queries there are many
MoveTasks that are all executed in sequence on the client. There's no real
reason for that - they could be run in parallel as well (i.e.: the stage graph
captures the dependencies and knows which tasks can happen in parallel)
Proposal here is to create a new config var:
hive.exec.parallel.movetask
When set to true it run movetasks in parallel also.)
> Optionally allow move tasks to run in parallel
> ----------------------------------------------
>
> Key: HIVE-8042
> URL: https://issues.apache.org/jira/browse/HIVE-8042
> Project: Hive
> Issue Type: Bug
> Reporter: Gunther Hagleitner
> Assignee: Gunther Hagleitner
> Attachments: HIVE-8042.1.patch, HIVE-8042.2.patch
>
>
> hive.exec.parallel allows one to run different stages of a query in parallel.
> However that applies only to map-reduce tasks. When using large multi insert
> queries there are many MoveTasks that are all executed in sequence on the
> client. There's no real reason for that - they could be run in parallel as
> well (i.e.: the stage graph captures the dependencies and knows which tasks
> can happen in parallel).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
