[
https://issues.apache.org/jira/browse/HIVE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207790#comment-14207790
]
Rui Li commented on HIVE-8793:
------------------------------
Hi [~xuefuz],
The failed tests are because I changed how {{ExplainTask}} prints maps: if the
map to print is a {{LinkedHashMap}}, it keeps the original order, rather than
re-order the map with a {{TreeMap}}. I did this to avoid printing like
following:
{code}
Reducer 3 <- Reducer 5
Reducer 4 <- Reducer 6
Reducer 5 <- Map1
Reducer 6 <- Map1
{code}
And change it to something like:
{code}
Reducer 5 <- Map1
Reducer 3 <- Reducer 5
Reducer 6 <- Map1
Reducer 4 <- Reducer 6
{code}
But problem is that even the LinkedHashMap's order can be non-deterministic. So
I'll revert this change as it's only a printing issue and well beyond the scope
here. I can create separate JIRA if you think it's worth the effort.
> 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
> Assignee: Rui Li
> Attachments: HIVE-8793.1-spark.patch
>
>
> 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)
