[
https://issues.apache.org/jira/browse/HIVE-8024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127509#comment-14127509
]
Chao commented on HIVE-8024:
----------------------------
Closing this JIRA as this approach seems not working or at least is hard to
implement.
[~xuefuz] is writing a design doc and we'll continue the discussion there.
> 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)
