[
https://issues.apache.org/jira/browse/YARN-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887322#comment-13887322
]
Karthik Kambatla commented on YARN-1461:
----------------------------------------
bq. Usually, what we do is to define a Java enum, use it in API records, and
map it to the corresponding proto class. The mapping is invoked in PBImpl of
the API records. Please take a look at YarnApplicationState and
YarnApplicationStateProto.
I see. Just looked at YarnApplicationState and YarnApplicationStateProto. We
could do something similar for this too. However, I am curious why having two
different enums, one in Java and one in proto, and a converter between the two
is preferable to just having one enum and no converter? Particularly, in this
case, it is always going to be a 1:1 mapping between the two.
> RM API and RM changes to handle tags for running jobs
> -----------------------------------------------------
>
> Key: YARN-1461
> URL: https://issues.apache.org/jira/browse/YARN-1461
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.2.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: yarn-1461-1.patch, yarn-1461-2.patch, yarn-1461-3.patch,
> yarn-1461-4.patch, yarn-1461-5.patch, yarn-1461-6.patch, yarn-1461-6.patch,
> yarn-1461-7.patch, yarn-1461-8.patch, yarn-1461-9.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
