[
https://issues.apache.org/jira/browse/HDFS-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546906#comment-13546906
]
Hudson commented on HDFS-4362:
------------------------------
Integrated in Hadoop-Mapreduce-trunk #1307 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1307/])
HDFS-4362. GetDelegationTokenResponseProto does not handle null token.
Contributed by Suresh Srinivas. (Revision 1430137)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1430137
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientNamenodeProtocolServerSideTranslatorPB.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientNamenodeProtocolTranslatorPB.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/proto/ClientNamenodeProtocol.proto
> 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: 3.0.0
>
> 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
