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

ASF GitHub Bot commented on HDFS-16710:
---------------------------------------

github-actions[bot] closed pull request #4670: HDFS-16710. Remove redundant 
throw exceptions in org.apache.hadoop.hdfs.server.namenode package
URL: https://github.com/apache/hadoop/pull/4670




> Remove redundant throw exceptions in org.apahce.hadoop.hdfs.server.namenode 
> package
> -----------------------------------------------------------------------------------
>
>                 Key: HDFS-16710
>                 URL: https://issues.apache.org/jira/browse/HDFS-16710
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: ZanderXu
>            Assignee: ZanderXu
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When I read some class about HDFS NameNode, I found there are many redundant 
> throw exception in org.apahce.hadoop.hdfs.server.namenode package, such as:
> {code:java}
> public synchronized void transitionToObserver(StateChangeRequestInfo req)
>     throws ServiceFailedException, AccessControlException, IOException {
>   checkNNStartup();
>   nn.checkHaStateChange(req);
>   nn.transitionToObserver();
> } {code}
> Because ServiceFailedException and AccessControlException is subClass of 
> IOException, so I feel that ServiceFailedException and AccessControlException 
> are redundant, so we can remove it to make code clearer, such as:
> {code:java}
> public synchronized void transitionToObserver(StateChangeRequestInfo req)
>     throws IOException {
>   checkNNStartup();
>   nn.checkHaStateChange(req);
>   nn.transitionToObserver();
> } {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to