[
https://issues.apache.org/jira/browse/HUDI-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sivabalan narayanan updated HUDI-3786:
--------------------------------------
Priority: Blocker (was: Major)
> 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
> Priority: Blocker
> Fix For: 0.11.0
>
>
> 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)
