hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2347) Consolidate RMStateVersion and NMDBSchemaVersion into StateVersion in yarn-server-common
Date Thu, 31 Jul 2014 07:06:38 GMT

    [ https://issues.apache.org/jira/browse/YARN-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080587#comment-14080587
] 

Zhijie Shen commented on YARN-2347:
-----------------------------------

Sorry for raising another issues so late. When I try to commit the patch, I realize ShuffleHandler
from MR project has a reference to Version. In this case,
{code}
@Private
@Unstable
public abstract class Version {
{code}
\@Private annotation seems not to be accurate. Moreover, other applications may implement
their AuxiliaryService as well, right? In this case, their AuxiliaryService is likely to use
Version as ShuffleHandler does. Therefore, should Version be \@Public instead, and be part
of o.a.h.y.api.records in hadoop-yarn-api?

> Consolidate RMStateVersion and NMDBSchemaVersion into StateVersion in yarn-server-common
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-2347
>                 URL: https://issues.apache.org/jira/browse/YARN-2347
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: YARN-2347-v2.patch, YARN-2347-v3.patch, YARN-2347-v4.patch, YARN-2347-v5.patch,
YARN-2347.patch
>
>
> We have similar things for version state for RM, NM, TS (TimelineServer), etc. I think
we should consolidate them into a common object.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message