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.

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

Debezium lost precision when data type is bigint or decimal #12064

Open
wk989898 opened this issue Feb 17, 2025 · 1 comment
Open

Debezium lost precision when data type is bigint or decimal #12064

wk989898 opened this issue Feb 17, 2025 · 1 comment

Comments

@wk989898
Copy link
Collaborator

wk989898 commented Feb 17, 2025

What did you do?

run debezium integration test

What did you expect to see?

the value lost precision

What did you see instead?

the value of which data type is bigint does not lose precision

Versions of the cluster

TiCDC version (execute cdc version):

master
@wk989898 wk989898 added area/ticdc Issues or PRs related to TiCDC. type/bug The issue is confirmed as a bug. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. labels Feb 17, 2025
@wk989898
Copy link
Collaborator Author

wk989898 commented Feb 17, 2025

According to the doc, the long type does not offer the greatest precision.
TiCDC implement mode:

bigint.unsigned.handling.mode: long
decimal.handling.mode: double
binary.handling.mode: base64

@wk989898 wk989898 removed affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. labels Feb 17, 2025
@jebter jebter added the impact/inconsistency incorrect/inconsistency/inconsistent label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants