[
https://issues.apache.org/jira/browse/HIVE-8024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126565#comment-14126565
]
Xuefu Zhang commented on HIVE-8024:
-----------------------------------
[~csun], thanks for the quick update. This is interesting. However, if union3
has two children, then cloning the plan and then remove union doesn't help
either as the cloned union also has two children. I don't know how this problem
can be resolved by cloning the plan.
I guess your case came from a multi-insert query, for which I think the logic
of multi-insert should kick in first. In this case, we would use a FS - TS to
separate the plan to multiple ones.
Thus, this might be unrelated. Could you continue the research, excluding
multi-insert cases?
> Find out whether it's possible to remove UnionOperator from original operator
> tree [Spark Branch]
> -------------------------------------------------------------------------------------------------
>
> Key: HIVE-8024
> URL: https://issues.apache.org/jira/browse/HIVE-8024
> Project: Hive
> Issue Type: Task
> Components: Spark
> Reporter: Chao
> Assignee: Chao
>
> Currently, after operator tree is processed, the generated works with union
> operators will go through {{GenSparkUtils::removeUnionOperators}}, which will
> clone the original operator plan associated with the work, and remove union
> operators in it. This caused some issues as seen, for example, in HIVE-7870.
> This JIRA is created to find out whether it's possible to just remove the
> union operators in the original plan.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
