[
https://issues.apache.org/jira/browse/HIVE-19237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493448#comment-16493448
]
Zoltan Haindrich commented on HIVE-19237:
-----------------------------------------
I think I've just fixed that, I modified it to use logicalEquals - I think it
will match on the appropriate nodes by this; the spark dpp tests seem to be
passing with it - but a full test execution may reveal problems:)
I wanted to drop a note to you...because I've seen that it's relatively new
code.
By the way the spark related changes are here:
https://github.com/kgyrtkirk/hive/commit/46aa288e1b020f0cd134bad29118636ed0cdc69d
Let me know if you think it may bump into problems!
> 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
>
>
> 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)
