[YARN-668] TokenIdentifier serialization should consider Unknown fields

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Target Version/s: 2.6.0
• Hadoop Flags: Incompatible change, Reviewed
• Assignee: Junping Du
• Reporter: Siddharth Seth
• Created: 10/May/13 23:54
• Updated: 16/May/18 23:45
• Resolved: 27/Sep/14 00:54

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.

Issue Links

• blocks: YARN-2558 Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId
• breaks: MAPREDUCE-6355 2.5 client cannot communicate with 2.5 job on 2.6 cluster
• breaks: YARN-8310 Handle old NMTokenIdentifier, AMRMTokenIdentifier, and ContainerTokenIdentifier formats
• is blocked by: YARN-2593 Many tests get failed on trunk
• relates to: YARN-2615 ClientToAMTokenIdentifier and DelegationTokenIdentifier should allow extended fields