[
https://issues.apache.org/jira/browse/HDDS-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264568#comment-17264568
]
Wei-Chiu Chuang commented on HDDS-4417:
---------------------------------------
I think that's fine.. l didn't realize OzoneConfigKeys is unstable API, so
incompat between minor releases are allowed.
I think from an application developer's perspective, it would be nice to to
tighten up the compat declaration (i.e. declare OzoneConfigKeys as Evolving
API) when we think the APIs are becoming mature. (1.0.0 would have been a good
time frame, but that ship has sailed). I can imagine configuration key APIs
being used extensively by applications so having compatible APIs makes upgrade
easier.
Also, do we have a guide for writing Ozone applications? Some example code
snippet can go a long way.
> Simplify Ozone client code with configuration object
> ----------------------------------------------------
>
> Key: HDDS-4417
> URL: https://issues.apache.org/jira/browse/HDDS-4417
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> In HDDS-4185 we agreed to introduce a new configuration for the Ozone client
> to adjust the behavior of incremental byte buffer.
> When I started to add it I realized the code is already very complex as all
> the required configuration values are propagated manually to the
> Key/Block/ChunkOutputstream as induvidual constructor parameters.
> In this patch I simplify the structure with using only one POJO with
> configuration annotations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
