[
https://issues.apache.org/jira/browse/HDFS-10764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429238#comment-15429238
]
Hudson commented on HDFS-10764:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10315 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10315/])
HDFS-10764. Fix INodeFile#getBlocks to not return null. Contributed by (jing9:
rev 0faee62a0c8c1b8fd83227babfd00fbc2b26bddf)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/INodeFile.java
> Fix INodeFile#getBlocks to not return null
> ------------------------------------------
>
> Key: HDFS-10764
> URL: https://issues.apache.org/jira/browse/HDFS-10764
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0-alpha2
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Fix For: 2.8.0
>
> Attachments: HDFS-10764.01.patch
>
>
> Not all callers of INodeFile#getBlocks check for null. e.g.
> {code}
> public final QuotaCounts storagespaceConsumedContiguous(
> BlockStoragePolicy bsp) {
> ...
> // Collect all distinct blocks
> Set<BlockInfo> allBlocks = new HashSet<>(Arrays.asList(getBlocks()));
> {code}
> We can either fix each caller or alternatively fix getBlocks to never return
> null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
