[
https://issues.apache.org/jira/browse/HUDI-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991712#comment-16991712
]
lamber-ken commented on HUDI-375:
---------------------------------
Hi, [~vinoth], after refactoring these, the code structure is concise and
clear, each component just care about its own options, and developers will use
these options easily.
Let's imagine a scenario, as hudi project growth, more and more components will
be introduced into project, their keys and default values are defined in a fat
config file. If use a parameter in a wrong place uncarefully, it may have a
great impact to us.
> 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)
