Adding vitess_hash function to ast #1089
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
|
|
This was referenced Nov 11, 2020
bezmax
changed the title
|
Build is failing because master is red. |
|
@Reminiscent, Thanks for your review. The bot only counts LGTMs from Reviewers and higher roles, but you're still welcome to leave your comments. See the corresponding SIG page for more information. Related SIG: ddl(slack). |
|
@kennytm Please help merge the PR. Thanks! |
|
PTAL @wjhuang2016 |
wjhuang2016
reviewed
Nov 25, 2020
ti-srebot
approved these changes
Dec 1, 2020
tiancaiamao
pushed a commit
to tiancaiamao/parser
that referenced
this pull request
Apr 27, 2021
Co-authored-by: Arenatlx <ailinsilence4@gmail.com>
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.
What problem does this PR solve?
Issue Number: pingcap/tidb#20971
Problem Summary: Implementing vitess_hash function to support efficient migration between tidb <-> vitess.
What is changed and how it works?
Proposal: pingcap/tidb#20971
What's Changed: New builtin_misc function added implementing vitess_hash algorithm.
Related changes
In order PRs need to be merged:
Release note
Added vitess_hash function which implements Vitess' hashing algorithm to determine sharding key.