[
https://issues.apache.org/jira/browse/HIVE-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131261#comment-14131261
]
Lefty Leverenz commented on HIVE-8042:
--------------------------------------
Should the description of *hive.exec.parallel* be revised in HiveConf.java,
since its behavior is changing in 0.14.0? (Sorry I didn't chime in earlier.)
Alternatively, the wiki could provide information about this change:
* [hive.exec.parallel |
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.exec.parallel]
> 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
> Fix For: 0.14.0
>
> Attachments: HIVE-8042.1.patch, HIVE-8042.2.patch, HIVE-8042.3.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)
