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

row level checksum calculation failed on timestamp value #50851

Closed
3AceShowHand opened this issue Jan 31, 2024 · 0 comments · Fixed by #50896
Closed

row level checksum calculation failed on timestamp value #50851

3AceShowHand opened this issue Jan 31, 2024 · 0 comments · Fixed by #50896
Assignees
Labels
affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. severity/moderate sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.

Comments

@3AceShowHand
Copy link
Contributor

3AceShowHand commented Jan 31, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

ref pingcap/tiflow#10573

1. Minimal reproduce step (Required)

set global tidb_enable_row_level_checksum=true;

set @@global.time_zone = '-05:00'

create table t (a int primary key, b timestamp);

insert into t values (1, '2023-02-09 13:00:00');

2. What did you expect to see? (Required)

When calculating checksum for timestamp value, should convert it to UTC, and then perform the calculation, to make the checksum value irrelevant to the time zone.

3. What did you see instead (Required)

Calculate checksum for the timestamp value based on time zone, this makes the downstream TiCDC changefeed verify changefeed failed, if the TiCDC server time zone is not the same as the TiDB.

4. What is your TiDB version? (Required)

master

@3AceShowHand 3AceShowHand added the type/bug The issue is confirmed as a bug. label Jan 31, 2024
@3AceShowHand 3AceShowHand self-assigned this Jan 31, 2024
@3AceShowHand 3AceShowHand added needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. labels Feb 1, 2024
ti-chi-bot pushed a commit to ti-chi-bot/tidb that referenced this issue Feb 2, 2024
ti-chi-bot pushed a commit to ti-chi-bot/tidb that referenced this issue Feb 2, 2024
@3AceShowHand 3AceShowHand added affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. labels Feb 2, 2024
ti-chi-bot bot pushed a commit that referenced this issue Feb 2, 2024
3AceShowHand added a commit to ti-chi-bot/tidb that referenced this issue Feb 2, 2024
3AceShowHand added a commit to ti-chi-bot/tidb that referenced this issue Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. severity/moderate sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants