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

Anu Engineer commented on HDDS-332:
-----------------------------------

[~dineshchitlangia] and [~nandakumar131]  Thanks for reviews. I have addressed 
most comments in v2 patch.

bq. Since we have only one storage handler, we can remove {{setStorageHandler}} 
and 

>From the code layering perspective, it is better to have the set and get 
>functions instead of taking a dependency on the Handler directly. During 
>startup, we will set the right value. So I have left that code as-is.

 

> Remove the ability to configure ozone.handler.type
> --------------------------------------------------
>
>                 Key: HDDS-332
>                 URL: https://issues.apache.org/jira/browse/HDDS-332
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Dinesh Chitlangia
>            Assignee: Anu Engineer
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-332.001.patch, HDDS-332.002.patch
>
>
> Based on feedback from [~anu] and [~xyao], logging this Jira to remove the 
> ability to configure ozone.handler.type.
> Currently, it can be configured with values - distributed or local.
> Value 'local' was strictly for internal testing purposes in initial stages. 
> By removing the configurability, we can avoid situations where users may end 
> up misconfiguring and running into issues.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to