[
https://issues.apache.org/jira/browse/HUDI-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Guo updated HUDI-8206:
----------------------------
Description: Right now MDT upgrade and downgrade process happens as part of
the data table upgrade and downgrade process (e.g., deleting unsupported MDT
partitions during downgrade) because the upgrade and downgrade process is only
invoked by the write client (MDT writes go through a separate write path, not
through the write client APIs). We should consider support upgrade and
downgrade of MDT directly through the write client so the table version and
configs can be handled properly. (was: Right now MDT upgrade and downgrade
process happens as part of the data table upgrade and downgrade process (e.g.,
deleting unsupported MDT partitions during downgrade) because the upgrade and
downgrade process is only invoked by the write client (MDT writes go through a
separate write path, not through the write client APIs). We should consider
support )
> Support upgrade and downgrade of MDT directly during MDT writes
> ---------------------------------------------------------------
>
> Key: HUDI-8206
> URL: https://issues.apache.org/jira/browse/HUDI-8206
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Ethan Guo
> Priority: Critical
> Fix For: 1.1.0
>
>
> Right now MDT upgrade and downgrade process happens as part of the data table
> upgrade and downgrade process (e.g., deleting unsupported MDT partitions
> during downgrade) because the upgrade and downgrade process is only invoked
> by the write client (MDT writes go through a separate write path, not through
> the write client APIs). We should consider support upgrade and downgrade of
> MDT directly through the write client so the table version and configs can be
> handled properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
