hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4362) GetDelegationTokenResponseProto does not handle null token
Date Tue, 08 Jan 2013 04:30:12 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Suresh Srinivas updated HDFS-4362:

       Resolution: Fixed
    Fix Version/s: 3.0.0
     Hadoop Flags: Incompatible change,Reviewed  (was: Incompatible change)
           Status: Resolved  (was: Patch Available)

Aaron, thanks for the review. I have committed the patch.
> 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

View raw message