Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG][CDC]Debezium Protocal set error default value for the not null timestamp field. #11966

Open
hk-lrzy opened this issue Jan 2, 2025 · 2 comments
Open

[BUG][CDC]Debezium Protocal set error default value for the not null timestamp field. #11966

hk-lrzy opened this issue Jan 2, 2025 · 2 comments
Labels
affects-8.5 This bug affects the 8.5.x(LTS) versions. area/ticdc Issues or PRs related to TiCDC. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@hk-lrzy
Copy link

hk-lrzy commented Jan 2, 2025 •
edited
Loading

{ "type": "string", "optional": false, "name": "io.debezium.time.ZonedTimestamp", "version": 1, "field": "Timestamp_Info", "default": 0 }

default value for the ZonedTimestamp is invalid.

follow is tidb ddl.
timestamp_Info timestamp default CURRENT_TIMESTAMP not null on update CURRENT_TIMESTAMP,
@hk-lrzy hk-lrzy changed the title [Question][CDC]Lose key value in kafka when protocal is debezium [Question][CDC]Debezium Protocol set error default value for the not null timestamp field. Jan 2, 2025
@hk-lrzy hk-lrzy changed the title [Question][CDC]Debezium Protocol set error default value for the not null timestamp field. [BUG][CDC]Debezium Protocol set error default value for the not null timestamp field. Jan 2, 2025
@hk-lrzy hk-lrzy changed the title [BUG][CDC]Debezium Protocol set error default value for the not null timestamp field. [BUG][CDC]Debezium Protocal set error default value for the not null timestamp field. Jan 2, 2025
@hongyunyan
Copy link
Collaborator

Debezium protocol is not supported in ticdc yet. We only support canal-json and open protocol in TiCDC now. We will support Debezium protocol soon.

@3AceShowHand 3AceShowHand transferred this issue from pingcap/ticdc Jan 3, 2025
@wk989898 wk989898 added type/bug The issue is confirmed as a bug. severity/moderate area/ticdc Issues or PRs related to TiCDC. affects-8.5 This bug affects the 8.5.x(LTS) versions. labels Jan 3, 2025
@hk-lrzy
Copy link
Author

hk-lrzy commented Jan 3, 2025 •
edited
Loading

Debezium protocol is not supported in ticdc yet. We only support canal-json and open protocol in TiCDC now. We will support Debezium protocol soon.

https://docs.pingcap.com/zh/tidb/stable/ticdc-debezium official website sad it's already supported, should it be removed if ticdc is not support it yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-8.5 This bug affects the 8.5.x(LTS) versions. area/ticdc Issues or PRs related to TiCDC. severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hk-lrzy @hongyunyan @wk989898