Details
Description
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.
Attachments
Attachments
Issue Links
- blocks
-
YARN-2558 Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId
- Closed
- breaks
-
MAPREDUCE-6355 2.5 client cannot communicate with 2.5 job on 2.6 cluster
- Resolved
-
YARN-8310 Handle old NMTokenIdentifier, AMRMTokenIdentifier, and ContainerTokenIdentifier formats
- Resolved
- is blocked by
-
YARN-2593 Many tests get failed on trunk
- Resolved
- relates to
-
YARN-2615 ClientToAMTokenIdentifier and DelegationTokenIdentifier should allow extended fields
- Closed