[
https://issues.apache.org/jira/browse/FLINK-35093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913966#comment-17913966
]
Vinh Pham commented on FLINK-35093:
-----------------------------------
hi [~loserwang1024] , i have a thought about this topic and for Postgresql,
replication slot already keep track of the confirmed_lsn and think we simplify
this issue by support a mode like COMMITED_OFFSET like Kafka connector
[https://github.com/apache/flink-connector-kafka/blob/f6a077a9dd8d1d5e43fc545cc9baab227d8438a0/flink-connector-kafka/src/main/java/org/apache/flink/connector/kafka/source/enumerator/initializer/OffsetsInitializer.java#L86]
instead of a SPECIFIC_OFFSET. This way user can choose the mode and can resume
automatically from a confirmed_lsn instead of providing a specific offset
What do you think about this idea? Should we change the scope to add a
COMMITTED_OFFSET mode ?
> Postgres source connector support SPECIFIC_OFFSETS start up mode from an
> existed replication slot.
> --------------------------------------------------------------------------------------------------
>
> Key: FLINK-35093
> URL: https://issues.apache.org/jira/browse/FLINK-35093
> Project: Flink
> Issue Type: Improvement
> Components: Flink CDC
> Affects Versions: cdc-3.1.0
> Reporter: Hongshun Wang
> Assignee: Vinh Pham
> Priority: Major
> Fix For: cdc-3.4.0
>
>
> Current, Postgres source connector only support INITIAL and LATEST mode.
> However, sometimes, user want to restart from an existed replication slot's
> confiermed_lsn.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
