You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2014/07/15 19:11:05 UTC

[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields

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

Vinod Kumar Vavilapalli commented on YARN-668:
----------------------------------------------

One other important point from the design doc at YARN-666 is to make sure that, during the upgrade, tokens are accepted by both the old and new NMs. We need some magic on the ResourceManager.

> TokenIdentifier serialization should consider Unknown fields
> ------------------------------------------------------------
>
>                 Key: YARN-668
>                 URL: https://issues.apache.org/jira/browse/YARN-668
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Vinod Kumar Vavilapalli
>
> This would allow changing of the TokenIdentifier between versions. The current serialization is Writable. A simple way to achieve this would be to have a Proto object as the payload for TokenIdentifiers, instead of individual fields.
> TokenIdentifier continues to implement Writable to work with the RPC layer - but the payload itself is serialized using PB.



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