[
https://issues.apache.org/jira/browse/HUDI-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990036#comment-16990036
]
Vinoth Chandar commented on HUDI-375:
-------------------------------------
I am okay with introducing a class that binds the key, config value together..
But I would like to not move the existing config classes much. Clients may be
configuring those using the HoodieWriteClient.Builder or as plain properties
passed infile, movingthem or renaming properties, will cause breakages.. we
cannot do that.
What exactly is in scope for this work?
> provide a mechanism which can extract some config items for specific
> component.
Whats the use-case for this?
Could you please clarify?
> 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)
