[
https://issues.apache.org/jira/browse/FLINK-37837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yanquan Lv resolved FLINK-37837.
--------------------------------
Fix Version/s: cdc-3.6.0
Assignee: Jia Fan
Resolution: Fixed
Fixed in master via 8d5be4488c6ce647d808e92fd5c437c88f1b3f59.
> Always Add create.table to include.schema.changes option
> --------------------------------------------------------
>
> Key: FLINK-37837
> URL: https://issues.apache.org/jira/browse/FLINK-37837
> Project: Flink
> Issue Type: Improvement
> Components: Flink CDC
> Affects Versions: cdc-3.4.0
> Reporter: Yanquan Lv
> Assignee: Jia Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: cdc-3.6.0
>
>
> `[include.schema.changes|https://nightlies.apache.org/flink/flink-cdc-docs-master/docs/core-concept/schema-evolution/#options]`
> indicate the support SchemaChange types of pipeline.
> Sometime user may only want to catch and process AddColumnEvent in their job,
> and the config of their yaml file may be written like:
> sink:
> type: starrocks
> ......
> include.schema.changes: [add.column]
> However, this job will meet the following exception because CreateTableEvent
> was ignored:
> Caused by: java.lang.IllegalStateException: Unable to coerce data record from
> third_data.table (schema: ......) to ods_test.route_table (schema: null)
> at
> org.apache.flink.cdc.runtime.operators.schema.regular.SchemaOperator.lambda$handleDataChangeEvent$1(SchemaOperator.java:214)
> ~[?:?]
> I believe that CreateTableEvent is the foundation for all our subsequent
> processing, so we should always add it to supported schema change types.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
