[
https://issues.apache.org/jira/browse/HIVE-19237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501393#comment-16501393
]
Zoltan Haindrich commented on HIVE-19237:
-----------------------------------------
there was an unstable set in mergejoinwork which made the order of the works
nondeterministic...and the q.out of explainuser_2 was sometimes failing because
of it...
> 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, HIVE-19237.07.patch,
> HIVE-19237.08.patch, HIVE-19237.08.patch, HIVE-19237.09.patch,
> HIVE-19237.10.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)
