[jira] [Closed] (HUDI-2776) Cluster update strategy should not be fenced by write config

["Ethan Guo (Jira)" <ji...@apache.org>]

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

Ethan Guo closed HUDI-2776.
---------------------------
    Resolution: Fixed

> Cluster update strategy should not be fenced by write config
> ------------------------------------------------------------
>
>                 Key: HUDI-2776
>                 URL: https://issues.apache.org/jira/browse/HUDI-2776
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: clustering, table-service
>    Affects Versions: 0.10.0
>            Reporter: sivabalan narayanan
>            Assignee: Sagar Sumit
>            Priority: Blocker
>             Fix For: 0.10.0
>
>
> In a multi-writer scenario, not all writers might set the enable clustering config. 
> BaseSparkCommitActionExecutor
> {code:java}
> private JavaRDD<HoodieRecord<T>> clusteringHandleUpdate(JavaRDD<HoodieRecord<T>> inputRecordsRDD) {
>   if (config.isClusteringEnabled()) {
>     Set<HoodieFileGroupId> fileGroupsInPendingClustering =
>         table.getFileSystemView().getFileGroupsInPendingClustering().map(entry -> entry.getKey()).collect(Collectors.toSet());
>     UpdateStrategy updateStrategy = (UpdateStrategy)ReflectionUtils
>         .loadClass(config.getClusteringUpdatesStrategyClass(), this.context, fileGroupsInPendingClustering);
>     return (JavaRDD<HoodieRecord<T>>)updateStrategy.handleUpdate(inputRecordsRDD);
>   } else {
>     return inputRecordsRDD;
>   }
> } {code}
> When clustering is scheduled and being executed by writer1, writer2 could go ahead and make updates to the same file group w/o any issues, given writer2 did not enable clustering in the write config. 
>  



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