[
https://issues.apache.org/jira/browse/HIVE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204808#comment-14204808
]
Xuefu Zhang edited comment on HIVE-8793 at 11/10/14 2:44 PM:
-------------------------------------------------------------
It's fine to make it a physical optimizer. For clone to work map, it seems we
can make it as a field of SparkWork.
However, this might be complicated in some cases. Let's do some research and
disable MJ optimization if it turns out to be too complicated.
was (Author: xuefuz):
It's fine to make it a physical optimizer. For clone to work map, it seems we
can make it as a field of SparkWork.
> Make sure multi-insert works with map join [Spark Branch]
> ---------------------------------------------------------
>
> Key: HIVE-8793
> URL: https://issues.apache.org/jira/browse/HIVE-8793
> Project: Hive
> Issue Type: Sub-task
> Components: Spark
> Affects Versions: spark-branch
> Reporter: Chao
>
> Currently, HIVE-8622 is implemented based on an assumption, that for a map
> join query, a BaseWork would not have multiple children. By testing through
> subquery_multiinsert.q did reveal that's the case. But, we need to
> investigate on this, and make sure this won't happen in general.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
