citusdata / citusdata/citus

[Feature question] CDC support in Citus

Open
#7,630 0 comments 0 reactions 0 assignees View on GitHub
needs-investigation
Dominant language
C
Stars
12.8k
Forks
794
Avg merge
2d 14h
Merged PRs (30d)
31

Description

I would like to ask you because I have some questions while testing the "CDC Support in Citus" feature provided from CITUS 11.3 version.

The following environments were tested first.

1. Citus version : 12.1.3
2. PostgreSQL version: 16.3
3. Debezium version: 2.5.0.Beta1

And the settings that [https://www.citusdata.com/updates/v11-3/#cdc_support](https://www.citusdata.com/updates/v11-3/#cdc_support) guides are also applied to all nodes.
citus.enable_change_data_capture='on'

Also, I followed the example and there are different results from the document.

1. CREATE PUBLICATION cdc_publication FOR TABLE sensors;
When creating publication in this way, the CDC Event of sensor table did not occur from the worker node.

2. CREATE PUBLICATION cdc_publication FOR ALL TABLES;
When creating publication in this way, the CDC Event of sensor table occurred from the worker node.
However, the document describes "This decoder translates any table name in the event from a partial shard name" as follows,
but the message that actually occurs was issued as sensors_$shardid.

3. The document explains, "For reference tables, this step is not required signs the changes to reference tables will be published only from co-ordinator node." However, during the test, the CDC event was not issued in the co-ordinator node with the reference table, and the event was generated in one of the worker nodes (nodeid 1).

Is there anything I'm missing in the setup by any chance?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.