[ https://issues.apache.org/jira/browse/TEZ-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514828#comment-14514828 ]
TezQA commented on TEZ-993: --------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12695488/TEZ-993-5.patch against master revision 21d4e2d. {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/552//console This message is automatically generated. > Remove application logic from RecoveryService > --------------------------------------------- > > Key: TEZ-993 > URL: https://issues.apache.org/jira/browse/TEZ-993 > Project: Apache Tez > Issue Type: Sub-task > Reporter: Bikas Saha > Assignee: Jeff Zhang > Attachments: TEZ-993-3.patch, TEZ-993-4.patch, TEZ-993-5.patch, > Tez-993-2.patch, Tez-993.patch > > > Currently RecoveryService storage logic knows a lot about the DAG like which > dag is pre-warm and does not need to be stored, which events needs special > treatment etc. This kind of logic couples the DAG and the storage more than > is probably necessary and can be a source of complications down the road. The > storage should ideally be simply storing a sequence of arbitrary records > delimited by a marker. -- This message was sent by Atlassian JIRA (v6.3.4#6332)