You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Wenning Ding (Jira)" <ji...@apache.org> on 2021/02/07 02:41:00 UTC
[jira] [Commented] (HUDI-89) Clean up placement, naming, defaults
of HoodieWriteConfig
[ https://issues.apache.org/jira/browse/HUDI-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280356#comment-17280356 ]
Wenning Ding commented on HUDI-89:
----------------------------------
Just have a question [~shivnarayan] [~vinoth], if we start using the ConfigOption structure, then users won't be able to use something like this any more?
{code:java}
.option(DataSourceWriteOptions.RECORDKEY_FIELD_OPT_KEY, "id")
{code}
> Clean up placement, naming, defaults of HoodieWriteConfig
> ---------------------------------------------------------
>
> Key: HUDI-89
> URL: https://issues.apache.org/jira/browse/HUDI-89
> Project: Apache Hudi
> Issue Type: Improvement
> Components: Code Cleanup, Usability, Writer Core
> Reporter: Vinoth Chandar
> Assignee: Vinoth Chandar
> Priority: Major
>
> # Rename HoodieWriteConfig to HoodieClientConfig
> # Move bunch of configs from CompactionConfig to StorageConfig
> # Introduce new HoodieCleanConfig
> # Should we consider lombok or something to automate the defaults/getters/setters
> # Consistent name of properties/defaults
> # Enforce bounds more strictly
--
This message was sent by Atlassian Jira
(v8.3.4#803005)