You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "lamber-ken (Jira)" <ji...@apache.org> on 2019/12/02 12:31:00 UTC

[jira] [Comment Edited] (HUDI-375) Refactor the configure framework of hudi project

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

lamber-ken edited comment on HUDI-375 at 12/2/19 12:30 PM:
-----------------------------------------------------------

I wrote a demo here, any suggestion are welcome, thanks.

[https://github.com/lamber-ken/hudi-config]

You can clone and run the test.


was (Author: lamber-ken):
I wrote a demo here, any suggestion are welcome, thanks.

https://github.com/lamber-ken/hudi-config

> 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)