[jira] [Resolved] (FLINK-35242) Add per-type schema evolution behavior configuration

["Leonard Xu (Jira)" <ji...@apache.org>]

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

Leonard Xu resolved FLINK-35242.
--------------------------------
    Resolution: Implemented

Implemented in master: 5ed9e05bdf00ae8b6e2df622e5e790a67335aa9d

> Add per-type schema evolution behavior configuration
> ----------------------------------------------------
>
>                 Key: FLINK-35242
>                 URL: https://issues.apache.org/jira/browse/FLINK-35242
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>            Reporter: yux
>            Assignee: yux
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: cdc-3.2.0
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> > Update: Changed `fine grained` terminology to avoid confusion between fine-grained job resource management feature.
> Currently, Flink CDC allows three SE strategy: evolving it, ignoring it, or throwing an exception. However such configuration strategy doesn't cover all user cases and requires want more fine-grained strategy configuration.
> This ticket suggests adding one more strategy "try_evolve" or "evolve_when_available". It's basically like "evolving" option, but doesn't throw an exception if such operation fails, which provides more flexibility.
> Also, this ticket suggests allowing user to configure per-schema-event strategy, so users could evolve some types of event (like rename column) and reject some unwelcomed events (like truncate table, remove column).



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