You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Raymond Xu (Jira)" <ji...@apache.org> on 2022/04/04 16:14:00 UTC

[jira] [Assigned] (HUDI-3782) Update metadata partitions table config when any of them is enabled/disabled

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

Raymond Xu reassigned HUDI-3782:
--------------------------------

    Assignee: Sagar Sumit

> Update metadata partitions table config when any of them is enabled/disabled
> ----------------------------------------------------------------------------
>
>                 Key: HUDI-3782
>                 URL: https://issues.apache.org/jira/browse/HUDI-3782
>             Project: Apache Hudi
>          Issue Type: Bug
>            Reporter: Sagar Sumit
>            Assignee: Sagar Sumit
>            Priority: Blocker
>             Fix For: 0.11.0
>
>
> Now that we have table configs for inflight and completed metadata partitions, and given that both reader and writer are going to rely on this config, we need to ensure that this config is updated properly even when any one of the metadata indexes is enabled/disabled.
> For instance, let's say user started with metadata enabled and colstats enabed. Colstats partition was fully built and the table config got updated. Now, they disable it and we miss to update table config. So the writers won't update the colstats partition and it would be out of sync. Readers think that the table config has it so it's already in sync but that's incorrect. We need to handle this scenario like how we did for top level metadata enable/disable config in HUDI-3451



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