discard the extended checksum part in row values #739
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Issue Number: ref pingcap/tidb#42747
Problem Description:
Row values now may have extended checksums since pingcap/tidb#42859, so client-java need to discard these checksums on read.
What is changed and how does it work?
Do not copy the checksum part to
RowV2.data
. Actually the current implementation is ok sinceRowV2.data
can be only accessed byRowV2.getData
. This PR just makes it more safer.