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

[jira] [Commented] (HUDI-3785) When any specific metadata table partition is disable, ensure to remove the entry from TableConfig

    [ https://issues.apache.org/jira/browse/HUDI-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17520901#comment-17520901 ] 

Sagar Sumit commented on HUDI-3785:
-----------------------------------

Fixed by [https://github.com/apache/hudi/pull/5222]

 

> When any specific metadata table partition is disable, ensure to remove the entry from TableConfig
> --------------------------------------------------------------------------------------------------
>
>                 Key: HUDI-3785
>                 URL: https://issues.apache.org/jira/browse/HUDI-3785
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: index, metadata
>    Affects Versions: 0.11.0
>            Reporter: sivabalan narayanan
>            Assignee: sivabalan narayanan
>            Priority: Blocker
>             Fix For: 0.11.0
>
>
> as of now, if entire metadata table is disabled, we ensure we delete the directory and update the table config wrt fully available MDT partitions. 
>  
> but if a user enables col stats and disables it after sometime, we don't update the table config to remove col stats. and so the data skipping might still be reading col stats and serving the queries which might lead to data loss. 
>  



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