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] [Commented] (HDFS-4362) GetDelegationTokenResponseProto does not handle null token
Date Wed, 16 Jan 2013 00:52:14 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554581#comment-13554581

Suresh Srinivas commented on HDFS-4362:

Incompatible means a contract is being broken. In this case it is wire protocol.

Incompatible change && does not affect any one does not make it compatible change.
That is the difference. Hence It is okay to say, this is an incompatible change, but will
not affect any body in production.
> 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

View raw message