tiflash: add upgrade.md doc#2182
Closed
ran-huang wants to merge 5 commits into
Closed
Conversation
ran-huang
added
translation/from-docs-cn
ilovesoup
approved these changes
Apr 7, 2020
Contributor
ilovesoup
left a comment
ilovesoup
left a comment
There was a problem hiding this comment.
This doc apply only to 3.1.
4.0 will be using tiup.
The rest of the content LGTM.
Contributor
Author
@ilovesoup Do you mean upgrading TiFlash using TiUP (pingcap/docs-cn#2636)? We can change the English content for v4.0 after the Chinese doc is ready. |
Contributor
|
@ran-huang It seems that the content in this PR is outdated.
|
Contributor
Author
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 is changed, added or deleted? (Required)
Add
upgrade.mddoc for TiFlash.Which TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-4.0, needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?