[
https://issues.apache.org/jira/browse/HUDI-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882468#comment-17882468
]
Ethan Guo commented on HUDI-7900:
---------------------------------
Since the upgrade and downgrade process is only invoked with the write client
(MDT writes go through a separate write path, not through the write client
APIs), we only did that for the data table, so deleting unsupported MDT
partitions should happen as part of the data table upgrade/downgrade process.
I filed a separate ticket to track better support of MDT upgrade and downgrade:
HUDI-8206
> Downgrade handles to delete new MDT partitions and cleanup MDT table
> properties
> -------------------------------------------------------------------------------
>
> Key: HUDI-7900
> URL: https://issues.apache.org/jira/browse/HUDI-7900
> Project: Apache Hudi
> Issue Type: Task
> Reporter: Sagar Sumit
> Assignee: Lin Liu
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> {code:java}
> {code}
> The newer metadata partitions such as secondary_index or partitin_stats etc
> are only meant for 1.x . So if someone had created these indexes and then
> later downgraded to 0.x then we need to ensure that hoodie.properties should
> not show these indexes as available. Ideally, we would want to drop the
> metadata partition altogether.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
