You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "sivabalan narayanan (Jira)" <ji...@apache.org> on 2021/03/29 03:21:00 UTC

[jira] [Commented] (HUDI-1675) Externalize all Hudi configurations

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

sivabalan narayanan commented on HUDI-1675:
-------------------------------------------

[~xiaotaotao]: May I know what's the intent here. If we have this, then for future writes, user does not need to set every config option and can just rely on existing options? is my understanding right. In general, what are the benefits from adding the configs to a file. 

> Externalize all Hudi configurations
> -----------------------------------
>
>                 Key: HUDI-1675
>                 URL: https://issues.apache.org/jira/browse/HUDI-1675
>             Project: Apache Hudi
>          Issue Type: Sub-task
>          Components: Spark Integration
>    Affects Versions: 0.9.0
>            Reporter: tao meng
>            Priority: Major
>             Fix For: 0.9.0
>
>
> # Externalize all Hudi configurations (separate configuration file)
>  # Save table related properties into hoodie.properties file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)