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-4367) GetDataEncryptionKeyResponseProto does not handle null response
Date Thu, 10 Jan 2013 16:02:13 GMT

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

Suresh Srinivas commented on HDFS-4367:
---------------------------------------

Aaron, in the wire protocol response a field is becoming from required to optional. That is
an incompatible change. It probably does not affect the correctly configured DFSClient users.
However for folks who are directly planning to use protobuf or using protobuf, this is a change.
I will add to the release note, this will not affect the DFSClient users.
                
> GetDataEncryptionKeyResponseProto  does not handle null response
> ----------------------------------------------------------------
>
>                 Key: HDFS-4367
>                 URL: https://issues.apache.org/jira/browse/HDFS-4367
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.2-alpha
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>         Attachments: HDFS-4367.patch
>
>
> GetDataEncryptionKeyResponseProto member dataEncryptionKey should be optional to handle
null response.

--
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

Mime
View raw message