point-get: calculate the row level checksum on the real time to avoid incorrect checksum caused by schema change

[3AceShowHand]

What problem does this PR solve?

Issue Number: close #52590

Problem Summary:

What changed and how does it work?

• tidb_row_checksum calculate the column-level checksum in the real time, instead of return the checksum store in the TiKV when the row inserted

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @3AceShowHand. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

Attention: Patch coverage is 67.27273% with 36 lines in your changes are missing coverage. Please review.

Project coverage is 74.6444%. Comparing base (c60f97d) to head (eedc297).
Report is 54 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #52511         +/-   ##
=================================================
+ Coverage   57.7692%   74.6444%   +16.8752%     
=================================================
  Files          1409       1511        +102     
  Lines        396668     449799      +53131     
=================================================
+ Hits         229152     335750     +106598     
+ Misses       150078      93812      -56266     
- Partials      17438      20237       +2799     

Flag	Coverage Δ
integration	49.2388% <26.3636%> (?)
unit	71.9719% <67.2727%> (+15.4364%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <ø> (∅)
parser	∅ <ø> (∅)
br	44.1379% <ø> (+43.4922%)	⬆️

[3AceShowHand]

/retest

[ti-chi-bot]

@3AceShowHand: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-lightning-integration-test	1b858cc	link	true	/test pull-lightning-integration-test
pull-br-integration-test	1b858cc	link	true	/test pull-br-integration-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[tangenta]

Will this be explained in user documentation?

[3AceShowHand]

I got your point, I think we can update the documentation to let user's know tat checksum only calculated on the new format.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-05-08 15:34:46.375250636 +0000 UTC m=+1062640.132386209: ☑️ agreed by zyguan.
• 2024-05-10 09:13:42.06271985 +0000 UTC m=+1212575.819855424: ☑️ agreed by tangenta.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tangenta, XuHuaiyu, zyguan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [XuHuaiyu,tangenta,zyguan]
• pkg/expression/OWNERS [XuHuaiyu]
• pkg/tablecodec/OWNERS [tangenta]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment