[
https://issues.apache.org/jira/browse/HDFS-16733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035703#comment-18035703
]
ASF GitHub Bot commented on HDFS-16733:
---------------------------------------
github-actions[bot] closed pull request #4761: HDFS-16733.Improve
INode#isRoot().
URL: https://github.com/apache/hadoop/pull/4761
> Improve INode#isRoot()
> ----------------------
>
> Key: HDFS-16733
> URL: https://issues.apache.org/jira/browse/HDFS-16733
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.3.0
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Major
> Labels: pull-request-available
>
> When constructing an INodeFile or INodeDirectory, it is usually necessary to
> give a name. For getLocalNameBytes, there are not many restrictions, such as
> null can be set. But an exception is thrown:
> {code:java}
> INodeDirectory root = new INodeDirectory(HdfsConstants.GRANDFATHER_INODE_ID,
> null, perm, 0L);
> {code}
> Some exceptions:
> {code:java}
> java.lang.NullPointerException
> at org.apache.hadoop.hdfs.server.namenode.INode.isRoot(INode.java:78)
> {code}
> Although these situations rarely occur in production environments, we should
> refine the implementation of isRoot() to avoid this exception. This can
> enhance system robustness.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
