[
https://issues.apache.org/jira/browse/HUDI-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991140#comment-16991140
]
Vinoth Chandar commented on HUDI-375:
-------------------------------------
[~lamber-ken] I'd like to always start from the problems. I checked out your
classes already. The Config class that holds a config key, value, default, and
may be a doc as well makes sense to me.
But, I remain skeptical on overall ROI if this would involve breaking existing
clients. lets start a DISCUSS thread and take it from therE?
> Refactor the configure framework of hudi project
> ------------------------------------------------
>
> Key: HUDI-375
> URL: https://issues.apache.org/jira/browse/HUDI-375
> Project: Apache Hudi (incubating)
> Issue Type: Improvement
> Reporter: lamber-ken
> Assignee: lamber-ken
> Priority: Major
>
> Currently, config items and their default value are dispersed in the java
> class file. It's easy to confuse when config items are defined more and more,
> so it's necessary to refactor the configure framework.
> May some things need to consider
> # config item and default value may defined in a class
> # provide a mechanism which can extract some config items for specific
> component.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
