[ https://issues.apache.org/jira/browse/HDFS-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554546#comment-13554546 ]
Todd Lipcon commented on HDFS-4362: ----------------------------------- I don't think this should be considered an incompatible change. In any case where an old server would return null, it would have thrown an error before responding. So this is just a bug fix on the server side. There's no case where an old client could have been working correctly against an old server but will stop working against a new server. Can you please show a scenario in which this could create an incompatibility between 2.0.2 and 2.0.3? > GetDelegationTokenResponseProto does not handle null token > ---------------------------------------------------------- > > Key: HDFS-4362 > URL: https://issues.apache.org/jira/browse/HDFS-4362 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 2.0.2-alpha > Reporter: Suresh Srinivas > Assignee: Suresh Srinivas > Priority: Critical > Fix For: 2.0.3-alpha > > Attachments: HDFS-4362.patch > > > While working on HADOOP-9173, I notice that the > GetDelegationTokenResponseProto declares the token field as required. However > return of null token is to be expected both as defined in > FileSystem#getDelegationToken() and also based on HDFS implementation. This > jira intends to make the field as optional. -- 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