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-4369) GetBlockKeysResponseProto does not handle null response
Date Mon, 14 Jan 2013 23:20:16 GMT

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

Suresh Srinivas updated HDFS-4369:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.3-alpha
     Release Note: 
Protobuf message GetBlockKeysResponseProto member keys is made optional from required so that
null values can be passed over the wire. This is an incompatible wire protocol change and
does not affect the API backward compatibility.

     Hadoop Flags: Incompatible change,Reviewed  (was: Incompatible change)
           Status: Resolved  (was: Patch Available)

I committed the patch to trunk and branch-2. Thank you Sanjay for the review.

                
> GetBlockKeysResponseProto does not handle null response
> -------------------------------------------------------
>
>                 Key: HDFS-4369
>                 URL: https://issues.apache.org/jira/browse/HDFS-4369
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.2-alpha
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>             Fix For: 2.0.3-alpha
>
>         Attachments: HDFS-4369.patch
>
>
> GetBlockKeysResponseProto#keys 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