1639501051135802_个人页

个人头像照片 1639501051135802
个人头像照片
0
1
0

个人介绍

暂无个人介绍

擅长的技术

获得更多能力
通用技术能力:

暂时未有相关通用技术能力~

云产品技术能力:

暂时未有相关云产品技术能力~

阿里云技能认证

详细说明
暂无更多信息

2022年07月

正在加载, 请稍后...
暂无更多信息
  • 回答了问题 2022-07-05

    请问postgresql cdc 怎么设置单独的增量模式呀,debezium.snapshot.mo

    同问,这几个配置都不生效

    Specifies the criteria for performing a snapshot when the connector starts:

    initial - The connector performs a snapshot only when no offsets have been recorded for the logical server name.

    always - The connector performs a snapshot each time the connector starts.

    never - The connector never performs snapshots. When a connector is configured this way, its behavior when it starts is as follows. If there is a previously stored LSN in the Kafka offsets topic, the connector continues streaming changes from that position. If no LSN has been stored, the connector starts streaming changes from the point in time when the PostgreSQL logical replication slot was created on the server. The never snapshot mode is useful only when you know all data of interest is still reflected in the WAL.

    initial_only - The connector performs an initial snapshot and then stops, without processing any subsequent changes.

    exported - The connector performs a snapshot based on the point in time when the replication slot was created. This is an excellent way to perform the snapshot in a lock-free way.

    custom - The connector performs a snapshot according to the setting for the snapshot.custom.class property, which is a custom implementation of the io.debezium.connector.postgresql.spi.Snapshotter interface.

    踩0 评论0
正在加载, 请稍后...
滑动查看更多
正在加载, 请稍后...
暂无更多信息