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

Posted to commits@hudi.apache.org by "Sagar Sumit (Jira)" <ji...@apache.org> on 2022/10/04 12:39:00 UTC

[jira] [Assigned] (HUDI-4974) Avoid creating Configuration copies in Hudi

     [ https://issues.apache.org/jira/browse/HUDI-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sagar Sumit reassigned HUDI-4974:
---------------------------------

    Assignee: Pratyaksh Sharma

> Avoid creating Configuration copies in Hudi
> -------------------------------------------
>
>                 Key: HUDI-4974
>                 URL: https://issues.apache.org/jira/browse/HUDI-4974
>             Project: Apache Hudi
>          Issue Type: Improvement
>            Reporter: Sagar Sumit
>            Assignee: Pratyaksh Sharma
>            Priority: Major
>             Fix For: 0.13.0
>
>
> See [https://github.com/apache/hudi/issues/6332] for more details.
> The reason for creating copies was to avoid ConcurrentModificationException encountered while long-running deltastreamer jobs. To avoid current modification, table meta client and file system get exclusive copies of the configuration. See [#755|https://github.com/apache/hudi/pull/755] for context.
> But this breaks when a wrapper configuration object is given to the constructor, e.g. HIveCachingHdfsConfiguration from Presto. Is there a way to avoid creating copies and make it work with whatever the engine provides?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)