Update Lightning import error handling #13376
Merged
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
lilin90
added
translation/from-docs-cn
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
ti-chi-bot
bot
added
the
size/S
|
@Frank945946 @ran-huang PTAL. Thanks! |
Frank945946
reviewed
Apr 27, 2023
Co-authored-by: Frank945946 <108602632+Frank945946@users.noreply.github.com>
|
/verify |
Frank945946
approved these changes
Apr 28, 2023
Frank945946
reviewed
Apr 28, 2023
|
/merge |
|
This pull request has been accepted and is ready to merge. Commit hash: 5ec8ac5
|
ti-chi-bot
bot
added
the
status/can-merge
15 tasks
|
In response to a cherrypick label: new pull request created to branch |
15 tasks
|
In response to a cherrypick label: new pull request created to branch |
15 tasks
|
In response to a cherrypick label: new pull request created to branch |
15 tasks
|
In response to a cherrypick label: new pull request created to branch |
lilin90
added
needs-cherry-pick-release-5.3
15 tasks
|
In response to a cherrypick label: new pull request created to branch |
15 tasks
|
In response to a cherrypick label: new pull request created to branch |
dveeden
added a commit
to dveeden/docs
that referenced
this pull request
May 1, 2023
### What is changed, added or deleted? (Required) - Expand `JOB_TYPE` documentation for `ADMIN SHOW DDL...` output. - Add note about `temp-dir` to `tidb_enabe_fast_regorg` docs. ### Which TiDB version(s) do your changes apply to? (Required) <!-- Fill in "x" in [] to tick the checkbox below.--> **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](https://github.com/pingcap/docs/blob/master/CONTRIBUTING.md#guideline-for-choosing-the-affected-versions). - [x] master (the latest development version) - [x] v7.1 (TiDB 7.1 versions) - [ ] v7.0 (TiDB 7.0 versions) - [ ] v6.6 (TiDB 6.6 versions) - [x] v6.5 (TiDB 6.5 versions) - [ ] v6.1 (TiDB 6.1 versions) - [ ] v5.4 (TiDB 5.4 versions) - [ ] v5.3 (TiDB 5.3 versions) - [ ] v5.2 (TiDB 5.2 versions) - [ ] v5.1 (TiDB 5.1 versions) - [ ] v5.0 (TiDB 5.0 versions) ### What is the related PR or file link(s)? <!--Reference link(s) will help reviewers review your PR quickly.--> - This PR is translated from: - Other reference link(s): ### Do your changes match any of the following descriptions? - [ ] Delete files - [ ] Change aliases - [ ] Need modification after applied to another branch <!-- If yes, please comment "/label version-specific-changes-required" below to trigger the bot to add the label. --> - [ ] Might cause conflicts after applied to another branch
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Jun 9, 2023
…anged, added or deleted? (Required) - Expand `JOB_TYPE` documentation for `ADMIN SHOW DDL...` output. - Add note about `temp-dir` to `tidb_enabe_fast_regorg` docs. ### Which TiDB version(s) do your changes apply to? (Required) <!-- Fill in "x" in [] to tick the checkbox below.--> **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](https://github.com/pingcap/docs/blob/master/CONTRIBUTING.md#guideline-for-choosing-the-affected-versions). - [x] master (the latest development version) - [x] v7.1 (TiDB 7.1 versions) - [ ] v7.0 (TiDB 7.0 versions) - [ ] v6.6 (TiDB 6.6 versions) - [x] v6.5 (TiDB 6.5 versions) - [ ] v6.1 (TiDB 6.1 versions) - [ ] v5.4 (TiDB 5.4 versions) - [ ] v5.3 (TiDB 5.3 versions) - [ ] v5.2 (TiDB 5.2 versions) - [ ] v5.1 (TiDB 5.1 versions) - [ ] v5.0 (TiDB 5.0 versions) ### What is the related PR or file link(s)? <!--Reference link(s) will help reviewers review your PR quickly.--> - This PR is translated from: - Other reference link(s): ### Do your changes match any of the following descriptions? - [ ] Delete files - [ ] Change aliases - [ ] Need modification after applied to another branch <!-- If yes, please comment "/label version-specific-changes-required" below to trigger the bot to add the label. --> - [ ] Might cause conflicts after applied to another branch
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.
What is changed, added or deleted? (Required)
Update the suggested handling method for the data inaccuracy error
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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?