[ 
https://issues.apache.org/jira/browse/HIVE-19237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495191#comment-16495191
 ] 

Rui Li commented on HIVE-19237:
-------------------------------

Thanks [~kgyrtkirk], I think it works. For this particular issue, seems you can 
simply make the marker a string instead of a set<string>.

What I had in mind was to pass the branching operator to cloneOperatorTree, so 
that we'll get the cloned branching operator back. Then we need to find cloned 
TS operators to set table meta data. The TS operators can be found using 
logicalEquals because TS must be root operators so they can be used 
interchangeably as long as they logically equal.

Please choose whichever way you think is simpler.

> 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)

Reply via email to