-
Notifications
You must be signed in to change notification settings - Fork 678
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*: refactor transaction documents #2088
*: refactor transaction documents #2088
Conversation
aa2cba1
to
05a6b38
Compare
@youjiali1995 PTAL |
@@ -26,7 +26,7 @@ We believe that being able to replicate in both directions lowers the risk when | |||
|
|||
TiDB internally shards table into small range-based chunks that we refer to as "Regions". Each Region defaults to approximately 100MiB in size, and TiDB uses a Two-phase commit internally to ensure that Regions are maintained in a transactionally consistent way. | |||
|
|||
Transactions in TiDB are strongly consistent, with snapshot isolation level consistency. For more information, see transaction [behavior and performance differences](/reference/transactions/transaction-model.md). This makes TiDB more comparable to traditional relational databases in semantics than some of the newer NoSQL systems using eventual consistency. | |||
Transactions in TiDB are strongly consistent, with snapshot isolation level consistency. For more information, see transaction [behavior and performance differences](/reference/transactions/transaction-isolation.md). This makes TiDB more comparable to traditional relational databases in semantics than some of the newer NoSQL systems using eventual consistency. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is irrelevant to the Chinese version.
Generally, I will replace transaction-model.md
(now deleted) with transaction-optimistic.md
. But here, according to the context, I replace it with transaction-isolation.md
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. But it doesn't apply to v2.1.
Sure. I will make dedicated changes when this PR is merged. Thanks! |
Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com>
Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com>
@yikeke PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM
Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com>
Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com>
Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com>
…el/docs into refactor-transaction
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-2.1 in PR #2156 |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-3.0 in PR #2157 |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-3.1 in PR #2158 |
* tools: add br tool doc and refine mydumper/loader doc * tools: add diagram * tools: adjust image size * tools: refine language * tools: refine language * maintain: update content * maintain: refine language * maintain: fix a typo * maintain: add working principles * maintain: refine introduction * maintain: refine format and layout * maintain: address comments from pingcap#2088 * maintainL refine language * maintain: minor language change * address comments * address comments * address comments * maintain: fix a typo * maintain: fix grammar error * maintain: fix a typo
What is changed, added or deleted? (Required)
Original PR: #1695 (closed)
This PR refactors and updates transaction-related documents, including:
Version differences: pingcap/docs-cn#2255
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-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?
TiKV | Distributed transaction
Shirly's Blog | Transaction in TIDB
Transaction in TiDB
Transaction Model | TiDB Documentation
Automatic retry and transactional anomalies caused by automatic retry