[
https://issues.apache.org/jira/browse/TEZ-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095090#comment-14095090
]
Hitesh Shah commented on TEZ-1384:
----------------------------------
One of the comments that Bikas had earlier was that there was code being
duplicated from InitTransition or StartTransition into the recovery flow
instead of both normal and recovery flow using the same transition logic with
the help of additional flags.
> Move recovery related code into inner class
> -------------------------------------------
>
> Key: TEZ-1384
> URL: https://issues.apache.org/jira/browse/TEZ-1384
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jeff Zhang
> Assignee: Jeff Zhang
> Attachments: Tez-1384.patch
>
>
> Currently each entity (DAG, Vertex, Task, TaskAttempt) has some common
> recovery code like log history event and restore from history event. These
> are 2 opposite aspects of recovery. One for store status while the other is
> for restore status. This jira is for putting these pieces of code together (
> in an inner class ). In this way, it is easy to maintain and cut down the
> possibility that one field is not stored or restored.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
