-
Notifications
You must be signed in to change notification settings - Fork 197
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
Use md5 checksum instead of crc32 #787
Conversation
15a8a93
to
dff78be
Compare
[LGTM Timeline notifier]Timeline:
|
/merge |
@Leavrth: We have migrated to builtin 👉 Please use
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 ti-community-infra/tichi repository. |
/test all |
/test unit-test |
@Leavrth: The specified target(s) for
Use In response to this:
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. |
/test pull-unit-test |
@Leavrth: The specified target(s) for
Use In response to this:
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. |
/test pull-verify |
/LGTM |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Leavrth 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:
Approvers can indicate their approval by writing |
/ok-to-test |
What problem does this PR solve?
Issue Number: close #634 #703
What is changed and how it works?
Change checksum algorithm to use md5 instead of crc32 to minimize chance of collision.
Essentially a copy of #707 that addresses merge conflicts and simplifies md5 checksum. Since md5 produces a 128-bit checksum, previous iteration attempted to track the checksum as two uint64s for lhs/rhs. This change simplifies the checksum query to bit_xor the lhs and the rhs into a single uint64 output.
Check List
Tests
Code changes
Side effects
Some previous concerns about pingcap/tidb#39576 and optimizing plan for checksum query rather than performing the same checksum operation twice for each lhs/rhs. Here's the explain output of the checksum query against a test table. I believe this shows that planner is pushing down the checksum functions down to the tikv coprocessor.
Related changes