executor: use EncodeBytes in countOriginDistinct #10225
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/run-all-tests |
XuHuaiyu
added a commit
to XuHuaiyu/tidb
that referenced
this pull request
Apr 25, 2019
zz-jason
pushed a commit
that referenced
this pull request
Apr 26, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I deleted the origin branch by mistaken and the origin PR #10107 was closed. So I file this new PR.
What problem does this PR solve?
fix issue #10099
What is changed and how it works?
Use EncodeBytes to encode string values in countOriginalWithDistinct.
Before this commit, string values are encoded with true values.
e.g.
encode("1", "122") --> "1122"
encode("11", "22") --> "1222"
These are not comparable.
Check List
Tests
Code changes
Side effects
N/A
Related changes