[
https://issues.apache.org/jira/browse/HIVE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204349#comment-14204349
]
Xuefu Zhang commented on HIVE-8793:
-----------------------------------
[~csun], I didn't mean doing HIVE-8118 before map join optimization, as my text
above stated. We only move the part of splitting SparkWork forward. Yes, we
can make that part of processing as a processor (either logical or physical).
Regardless, I think this is a matter of refactoring.
Could you please move on to HIVE-8776 as it seems blocking the rest of map join
work?
> 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)
