[
https://issues.apache.org/jira/browse/HIVE-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224712#comment-14224712
]
Chao commented on HIVE-8536:
----------------------------
[~lirui] Yes, I remember dependency task is for multi-insert, so that move
tasks won't start until all inserts are done. In Tez it always create such a
task, which I'm not sure why. I think it makes sense to change it to MR's
approach.
BTW, will it solves the issue in this JIRA completely? Is it possible that skew
join is mixed with multi-insert in the same query, and you still end up with
more than one child tasks?
> Enable SkewJoinResolver for spark [Spark Branch]
> ------------------------------------------------
>
> Key: HIVE-8536
> URL: https://issues.apache.org/jira/browse/HIVE-8536
> Project: Hive
> Issue Type: Improvement
> Components: Spark
> Reporter: Rui Li
> Assignee: Rui Li
> Attachments: HIVE-8536.1-spark.patch, HIVE-8536.2-spark.patch
>
>
> Sub-task of HIVE-8406
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)