Parse routes in legacy MAD #1361
Open
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 code is backported from async. To receive Route protos, you must be running the latest legacy PD. I did not create a DB migration for this. Just paste the table creation that you see in the code into mysql/mariadb. I have not tested this exact code, as I run a modified version of legacy MAD. But I'm pretty confident this is fine.
comstud
force-pushed
the
upstream-legacy-routes
branch
from
1652da9 to
b07de5a
Compare
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.
This code is backported from async. To receive Route protos, you must be running the latest legacy PD.
I did not create a DB migration for this. Just paste the table creation that you see in the code into mysql/mariadb.
I have not tested this exact code, as I run a modified version of legacy MAD. But I'm pretty confident this is fine.