br: pitr filter feature release doc #20450
Conversation
Signed-off-by: Wenqi Mou <[email protected]>
ti-chi-bot
bot
added
missing-translation-status
lilin90
added
the
translation/from-docs
ti-chi-bot
bot
removed
the
missing-translation-status
There was a problem hiding this comment.
Pull Request Overview
This PR updates the BR documentation by introducing a new section on using filters during PITR operations, as well as adding a new section on concurrent recovery operations.
- Introduces step-by-step instructions and examples for using filters to restore specific databases or tables.
- Adds documentation on how to perform concurrent PITR operations with sample commands and important notes regarding usage limitations.
Comments suppressed due to low confidence (1)
br/br-pitr-manual.md:573
- [nitpick] Including an example or additional details to clarify what constitutes overlapping data sets could help users avoid potential misuse of concurrent PITR operations.
> - 每个并发恢复操作必须针对不同的数据库或非重叠的表集合。尝试并发恢复重叠数据集将导致错误。
br/br-pitr-manual.md
Outdated
| ### 进行中的日志备份与快照恢复的兼容性 | ||
|
|
||
| 从 v9.0.0 开始，当存在日志备份任务时，如果**同时满足**以下条件，则可以正常进行快照恢复 (`br restore [full|database|table]`)，并且恢复的数据可以被进行中的日志备份（下称“日志备份”）正常记录： | ||
| 从 v9.0.0 开始，当存在日志备份任务时，如果**同时满足**以下条件，则可以正常进行快照恢复 (`br restore [full|database|table]`)，并且恢复的数据可以被进行中的日志备份（下称"日志备份"）正常记录： |
There was a problem hiding this comment.
Consider aligning the style of quotation marks used for '日志备份' consistently throughout the document to enhance clarity.
Copilot uses AI. Check for mistakes.
lilin90
added
the
do-not-merge/hold
Co-authored-by: Lilian Lee <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@lilin90 thanks for the detailed review! |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?