[
https://issues.apache.org/jira/browse/HIVE-19237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494782#comment-16494782
]
Rui Li commented on HIVE-19237:
-------------------------------
[~kgyrtkirk], I agree storing origin ID is not ideal and I'd be happy to stop
relying on operator ID if there's another reliable way to associate cloned
operators.
Let's go the logicalEquals way (patch v5) to unblock your work here. I'll open
a follow up for the Spark code. Sorry about the back and forth.
> Only use an operatorId once in a plan
> -------------------------------------
>
> Key: HIVE-19237
> URL: https://issues.apache.org/jira/browse/HIVE-19237
> Project: Hive
> Issue Type: Bug
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Attachments: HIVE-19237.01.patch, HIVE-19237.02.patch,
> HIVE-19237.03.patch, HIVE-19237.04.patch, HIVE-19237.05.patch,
> HIVE-19237.05.patch, HIVE-19237.06.patch
>
>
> Column stats autogather plan part is added from a plan compiled by the driver
> itself; however that driver starts to use operatorIds from 1 ; so it's
> possible that 2 SEL_1 operators end up in the same plan...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
