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

Posted to commits@hudi.apache.org by "Ethan Guo (Jira)" <ji...@apache.org> on 2022/04/02 19:02:00 UTC

[jira] [Closed] (HUDI-3451) Add checks for metadata table init to avoid possible out-of-sync

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

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

> Add checks for metadata table init to avoid possible out-of-sync
> ----------------------------------------------------------------
>
>                 Key: HUDI-3451
>                 URL: https://issues.apache.org/jira/browse/HUDI-3451
>             Project: Apache Hudi
>          Issue Type: Bug
>            Reporter: Ethan Guo
>            Assignee: Ethan Guo
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 0.11.0
>
>
> Around guarding enabling and disabling MDT. i.e. if someone enabled MDT and after few commits disables MDT and then re-enables it, we should re-bootstrap the MDT. So, we were wondering if we can add the "metadata.enable" property to table config. So, when someone disable MDT, we can clean up the MDT right away.  We don't leave any trails and don't need to worry about when the user will re-enable it back. 



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