[
https://issues.apache.org/jira/browse/HDFS-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553258#comment-13553258
]
Hudson commented on HDFS-4369:
------------------------------
Integrated in Hadoop-trunk-Commit #3228 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/3228/])
HDFS-4369. GetBlockKeysResponseProto does not handle null response.
Contributed by Suresh Srinivas. (Revision 1433206)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1433206
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/NamenodeProtocolServerSideTranslatorPB.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/NamenodeProtocolTranslatorPB.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/proto/NamenodeProtocol.proto
> 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
