[
https://issues.apache.org/jira/browse/YARN-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669738#comment-13669738
]
Omkar Vinit Joshi commented on YARN-717:
----------------------------------------
why do we need to keep
ClientTokenPBImpl/ContainerTokenPBImpl/DelegationTokenPBImpl? can't we just
remove that too?
> Copy BuilderUtil methods into token-related records
> ---------------------------------------------------
>
> Key: YARN-717
> URL: https://issues.apache.org/jira/browse/YARN-717
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jian He
> Assignee: Jian He
> Attachments: YARN-717.1.patch, YARN-717.2.patch
>
>
> This is separated from YARN-711,as after changing yarn.api.token from
> interface to abstract class, eg: ClientTokenPBImpl has to extend two classes:
> both TokenPBImpl and ClientToken abstract class, which is not allowed in JAVA.
> We may remove the ClientToken/ContainerToken/DelegationToken interface and
> just use the common Token interface
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
