[
https://issues.apache.org/jira/browse/HIVE-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245131#comment-16245131
]
Prasanth Jayachandran commented on HIVE-17904:
----------------------------------------------
logic looks good to me. +1, pending tests.
btw, file HIVE-18027 to explore the option of using Tez application id or
attempt id as a unique incrementing identifier.
> handle internal Tez AM restart in registry and WM
> -------------------------------------------------
>
> Key: HIVE-17904
> URL: https://issues.apache.org/jira/browse/HIVE-17904
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-17904.01.patch, HIVE-17904.patch, HIVE-17904.patch
>
>
> After the plan update patch is committed. The current code doesn't account
> very well for it; registry may have races, and an event needs to be added to
> WM when some AM resets, at least to make sure we discard the update errors
> that pertain to the old AM.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
