[
https://issues.apache.org/jira/browse/HUDI-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sivabalan narayanan updated HUDI-9638:
--------------------------------------
Description:
When a user creates a new table in v9 w/ payload configs, we should do the same
mapping we do w/ 8 -> 9 upgrade handler and only injet table props relating to
merge modes. for eg, we don't want to see regular payload class config in table
config for v9 table (could be a separate PR in itself). Don't think failing the
writes will be a good user exp. So, lets do the mapping programmatically and
let the writes succeed. May be we can add a warn log to call out whats the
recommended flow or what configs we expect the user to set.
*
** We also have validations for subsequent writes to check that new writer
props match w/ those in table properties. you may have to fix the validation to
account for this as well.
was:when a table is created in V9, with payload, we should handle its table
config properly.
> Fix table creation logic for payload deprecation
> -------------------------------------------------
>
> Key: HUDI-9638
> URL: https://issues.apache.org/jira/browse/HUDI-9638
> Project: Apache Hudi
> Issue Type: Sub-task
> Reporter: Lin Liu
> Assignee: Lin Liu
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> When a user creates a new table in v9 w/ payload configs, we should do the
> same mapping we do w/ 8 -> 9 upgrade handler and only injet table props
> relating to merge modes. for eg, we don't want to see regular payload class
> config in table config for v9 table (could be a separate PR in itself). Don't
> think failing the writes will be a good user exp. So, lets do the mapping
> programmatically and let the writes succeed. May be we can add a warn log to
> call out whats the recommended flow or what configs we expect the user to set.
> *
> ** We also have validations for subsequent writes to check that new writer
> props match w/ those in table properties. you may have to fix the validation
> to account for this as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
