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 2022/04/03 19:38:00 UTC

[jira] [Created] (HUDI-3786) how to deduce what MDT partitions to update on the write path w/ async indeing

sivabalan narayanan created HUDI-3786:
-----------------------------------------

             Summary: how to deduce what MDT partitions to update on the write path w/ async indeing
                 Key: HUDI-3786
                 URL: https://issues.apache.org/jira/browse/HUDI-3786
             Project: Apache Hudi
          Issue Type: Bug
          Components: metadata
            Reporter: sivabalan narayanan


w/ async indexing, how do we deduce what are the MDT partitions to update on the regular write path? 

 
{code:java}
private MetadataRecordsGenerationParams getRecordsGenerationParams() {
  return new MetadataRecordsGenerationParams(
      dataMetaClient, enabledPartitionTypes, dataWriteConfig.getBloomFilterType(),
      dataWriteConfig.getBloomIndexParallelism(),
      dataWriteConfig.isMetadataColumnStatsIndexEnabled(),
      dataWriteConfig.getColumnStatsIndexParallelism(),
      StringUtils.toList(dataWriteConfig.getColumnsEnabledForColumnStatsIndex()),
      StringUtils.toList(dataWriteConfig.getColumnsEnabledForBloomFilterIndex()));
} {code}
As of now, I see above code snippet is what deciding that. But don't we need to decide on tableConfig ? 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)