[jira] [Updated] (TEZ-1384) Move recovery related code into inner class
[ https://issues.apache.org/jira/browse/TEZ-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1384: Attachment: Tez-1384-2.patch 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-2.patch, 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.3.4#6332)
[jira] [Updated] (TEZ-1384) Move recovery related code into inner class
[ https://issues.apache.org/jira/browse/TEZ-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1384: Description: 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. Move recovery related code into inner class --- Key: TEZ-1384 URL: https://issues.apache.org/jira/browse/TEZ-1384 Project: Apache Tez Issue Type: Improvement Reporter: Jeff Zhang Assignee: Jeff Zhang 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)
[jira] [Updated] (TEZ-1384) Move recovery related code into inner class
[ https://issues.apache.org/jira/browse/TEZ-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1384: Attachment: Tez-1384.patch 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)
