[ 
https://issues.apache.org/jira/browse/FLINK-37479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945988#comment-17945988
 ] 

Vinh Pham commented on FLINK-37479:
-----------------------------------

Hi [~loserwang1024] , I've read your doc about this but I'm still not clear on 
what the challenge is, could you help to elaborate a bit more on that. Is the 
concern about not detecting the changes are from leaf or parent table?

I recall that if we use option publish_via_partition_root, it will return event 
as parent table and we shouldn't concern about the leaf table at all? I recall 
that how it works on debezium, just want to understand more on what is the 
difference between flink-cdc and debezium that makes this difficult.

I can help to contribute to this and this is quite important for my use case, 
almost all of the tables in my team are partitioned tables.

> postgres cdc connector support discover PARTITIONED TABLE
> ---------------------------------------------------------
>
>                 Key: FLINK-37479
>                 URL: https://issues.apache.org/jira/browse/FLINK-37479
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>            Reporter: Vinh Pham
>            Priority: Minor
>
> At the moment, Postgresql connector doesn't support discover PARTITIONED 
> TABLE, making the connector not possible to take snapshot on partitioned 
> table.
> [https://github.com/apache/flink-cdc/blob/master/flink-cdc-connect/flink-cdc-source-connectors/flink-connector-postgres-cdc/src/main/java/org/apache/flink/cdc/connectors/postgres/source/utils/TableDiscoveryUtils.java#L41]
>  
> This is inconsistent with the other implementation in PostgresConnection 
> class 
> [https://github.com/apache/flink-cdc/blob/master/flink-cdc-connect/flink-cdc-source-connectors/flink-connector-postgres-cdc/src/main/java/io/debezium/connector/postgresql/connection/PostgresConnection.java#L859]



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

Reply via email to