[
https://issues.apache.org/jira/browse/HIVE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204700#comment-14204700
]
Rui Li commented on HIVE-8793:
------------------------------
Hi [~xuefuz], do you mean the job here is just to make
{{SparkPlanGenerator.splitSparkWork}} an optimizer and move it to
{{SparkCompiler}}? Since we have to split/clone BaseWork, I think it's easier
to make it a physical optimizer, right?
Besides, as [~csun] mentioned, {{SparkPlanGenerator.cloneToWork}} can't be used
after the refactor. Do you think we have to deal with that?
> 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: 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)
