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 2023/02/07 22:53:01 UTC

[jira] [Updated] (HUDI-5075) Add support to rollback residual clustering after disabling clustering

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

Ethan Guo updated HUDI-5075:
----------------------------
    Fix Version/s: 0.14.0
                       (was: 0.13.0)

> Add support to rollback residual clustering after disabling clustering
> ----------------------------------------------------------------------
>
>                 Key: HUDI-5075
>                 URL: https://issues.apache.org/jira/browse/HUDI-5075
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: clustering
>            Reporter: sivabalan narayanan
>            Assignee: sivabalan narayanan
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 0.14.0
>
>
> if a user enabled clustering and after sometime disabled it due to whatever reason, there is a chance that there is a pending clustering left in the timeline. But once clustering is disabled, this could just be lying around. but this could affect metadata table compaction whcih in turn might affect the data table archival. 
> so, we need a way to fix this. 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)