hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-947) Defining the history data classes for the implementation of the reading/writing interface
Date Thu, 30 Jan 2014 06:44:11 GMT

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

Vinod Kumar Vavilapalli updated YARN-947:
-----------------------------------------

    Fix Version/s:     (was: YARN-321)
                   2.4.0

YARN-321 branch is merged into trunk and branch-2. Setting fix-version of all committed patches
under YARN-321 to be 2.4.0.

> 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: 2.4.0
>
>         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, YARN-947.9.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.5#6160)

Mime
View raw message