hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields
Date Thu, 17 Jul 2014 03:22:05 GMT

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

Junping Du commented on YARN-668:
---------------------------------

Hi [~vinodkv], I think here we are talking about to handle changes like YARN-2152. Isn't it?
I think there are basically two steps there: 
1. Make new token implementation can deserialize old token so all persistent old tokens can
still live when new implementation is up.
2. Make RM can accept both old tokens and new tokens. 
Step 1 is more fundamental and also related to step 2. Do we think we should have a RPCWrapper
class to wrap all TokenIdentifier classes with encode/decode a proto class for new added fields
in future?

> 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)

Mime
View raw message