[ 
https://issues.apache.org/jira/browse/HIVE-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-17904:
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

Committed to master. Thanks for the review!

> 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
>             Fix For: 3.0.0
>
>         Attachments: HIVE-17904.01.patch, HIVE-17904.02.patch, 
> HIVE-17904.03.patch, HIVE-17904.04.patch, HIVE-17904.05.patch, 
> HIVE-17904.06.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)

Reply via email to