[
https://issues.apache.org/jira/browse/FLINK-38271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017010#comment-18017010
]
Artur commented on FLINK-38271:
-------------------------------
[~ouyangwuli] Hello!
I'm currently working on a project that involves schema evolution in Postgres.
I've been thinking about how to best handle it, and I think that if there are
changes in schema of DataChangeEvent (like renaming columns, adding columns,
etc), we'll need to re-discover the schema of the table from the source. But
I'm worried about the speed and performance of the load process after these
changes. I was wondering how you plan to handle schema evolution, and if you've
got any tips or tricks up your sleeve.
> PostgresSQL pipeline supports table schema evolution.
> -----------------------------------------------------
>
> Key: FLINK-38271
> URL: https://issues.apache.org/jira/browse/FLINK-38271
> Project: Flink
> Issue Type: Improvement
> Components: Flink CDC
> Affects Versions: cdc-3.5.0
> Reporter: ouyangwulin
> Assignee: ouyangwulin
> Priority: Critical
>
> PostgreSQL obtains incremental data from the log log parsing, the current
> parser does not support DDL, but we can deduce the table structure from the
> schema information, so it is also possible to implement table structure
> evolution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
