Skip to content

tiflash: add use-tiflash doc (#2163)#2173

Merged
yikeke merged 1 commit into
pingcap:release-3.1from
sre-bot:release-3.1-6d78da53a8d4
Apr 7, 2020
Merged

tiflash: add use-tiflash doc (#2163)#2173
yikeke merged 1 commit into
pingcap:release-3.1from
sre-bot:release-3.1-6d78da53a8d4

Conversation

@sre-bot
Copy link
Copy Markdown
Contributor

@sre-bot sre-bot commented Apr 7, 2020

cherry-pick #2163 to release-3.1


What is changed, added or deleted? (Required)

Add Use TiFlash document.

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version, including v4.0 changes for now)
  • v3.1 (TiDB 3.1 versions)
  • v3.0 (TiDB 3.0 versions)
  • v2.1 (TiDB 2.1 versions)

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-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.

What is the related PR or file link(s)?

* tiflash: add use-tiflash doc

* Apply suggestions from code review

Co-Authored-By: Ran <huangran@pingcap.com>

* use unordered list

* fix typos

* Update use-tiflash.md

* Update reference/tiflash/use-tiflash.md

Co-Authored-By: Ran <huangran@pingcap.com>

Co-authored-by: Ran <huangran@pingcap.com>
Co-authored-by: Soup <maxiaoyu@pingcap.com>
Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com>
@sre-bot sre-bot mentioned this pull request Apr 7, 2020
4 tasks
@sre-bot sre-bot added type/cherry-pick-for-release-3.1 This PR is cherry-picked to release-3.1 from a source PR. v4.0 This PR/issue applies to TiDB v4.0. labels Apr 7, 2020
@yikeke yikeke merged commit 33d00cb into pingcap:release-3.1 Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type/cherry-pick-for-release-3.1 This PR is cherry-picked to release-3.1 from a source PR. v4.0 This PR/issue applies to TiDB v4.0.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants