-
Notifications
You must be signed in to change notification settings - Fork 696
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
TiDB auto increment MySQL-compatible behavior clarification (#20152) #20286
Merged
ti-chi-bot
merged 8 commits into
pingcap:release-8.4
from
ti-chi-bot:cherry-pick-20152-to-release-8.4
Feb 13, 2025
Merged
TiDB auto increment MySQL-compatible behavior clarification (#20152) #20286
ti-chi-bot
merged 8 commits into
pingcap:release-8.4
from
ti-chi-bot:cherry-pick-20152-to-release-8.4
Feb 13, 2025
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
- Update GitHub repository links from tidb-tools to tiflow - Add TiUP installation method for v9.0.0+ - Update Docker image references - Add version-specific installation instructions - Update download-ecosystem-tools.md with new package information
Update Docker image for sync-diff-inspector The previous `docker pull pingcap/tiflow:latest` command was incorrect. After confirming with Flare Zuo (R&D Group - Engineering Productivity - Efficiency & Ops team), we should use `docker pull pingcap/sync-diff-inspector:latest` to align with TiCDC and DM, ensuring consistency across TiFlow-managed images. This update reflects the correct image name for better usability.
This commit improves the documentation by: Adding clearer introduction and benefits, including practical examples of ID allocation, adding comparison between AUTO_ID_CACHE modes, restructuring version-specific notes, and adding v8.1.0 forceRebase information
Co-authored-by: xixirangrang <[email protected]>
15 tasks
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lilin90 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
lgtm
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
type/cherry-pick-for-release-8.4
type/enhancement
The issue or PR belongs to an enhancement.
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.
This is an automated cherry-pick of #20152
What is changed, added or deleted? (Required)
Improved the MySQL compatibility mode section in auto-increment.md by:
AUTO_ID_CACHE 1
and default modeThese changes make it easier for users to:
Which TiDB version(s) do your changes apply to? (Required)
Since this change includes information about behavior changes across multiple versions (v6.4.0 and v8.1.0) and documents current functionality, it should be applied to:
What is the related PR or file link(s)?
N/A
Do your changes match any of the following descriptions?