[ https://issues.apache.org/jira/browse/YARN-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803639#comment-13803639 ]
Hadoop QA commented on YARN-947: -------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12609967/YARN-947.8.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2271//console This message is automatically generated. > Defining the history data classes for the implementation of the > reading/writing interface > ----------------------------------------------------------------------------------------- > > Key: YARN-947 > URL: https://issues.apache.org/jira/browse/YARN-947 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Zhijie Shen > Assignee: Zhijie Shen > Fix For: YARN-321 > > Attachments: YARN-947.1.patch, YARN-947.2.patch, YARN-947.3.patch, > YARN-947.4.patch, YARN-947.5.patch, YARN-947.6.patch, YARN-947.8.patch > > > We need to define the history data classes have the exact fields to be > stored. Therefore, all the implementations don't need to have the duplicate > logic to exact the required information from RMApp, RMAppAttempt and > RMContainer. > We use protobuf to define these classes, such that they can be ser/des > to/from bytes, which are easier for persistence. -- This message was sent by Atlassian JIRA (v6.1#6144)