LiXin Ge commented on HDFS-13333:

Hi, [~nandakumar131] [~elek], the Ozone branch moves so fast, that's amazing.

After  HDFS-13395 contributed by [~nandakumar131],  
{{HddsDatanodeService#HddsDatanodeService}} integrated to 
{{HddsDatanodeService#start}}, and as discussed with [~elek], 
{{HddsDatanodeService#start}} should better not throw any checked exception, So 
seems there is no need to Introduce a new exception here that what's this Jira 
tried to do?

> Ozone: Introduce a new SCM Exception which will be thrown when mandatory 
> property is missing 
> ---------------------------------------------------------------------------------------------
>                 Key: HDFS-13333
>                 URL: https://issues.apache.org/jira/browse/HDFS-13333
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Nanda kumar
>            Assignee: LiXin Ge
>            Priority: Major
>              Labels: newbie
>         Attachments: HDFS-13333-HDFS-7240.001.patch, 
> HDFS-13333-HDFS-7240.002.patch, HDFS-13333-HDFS-7240.003.patch, 
> HDFS-13333.001.patch
> It's better to have a separate SCM Exception to indicate a missing mandatory 
> property. This was proposed by [~xyao] in  [this comment| 
> https://issues.apache.org/jira/browse/HDFS-13300?focusedCommentId=16408553&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16408553]

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to