-
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
TiDB auto increment MySQL-compatible behavior clarification #20152
Conversation
- 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
/cc @Frank945946 |
@alastori: GitHub didn't allow me to request PR reviews from the following users: frank945946. Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@Frank945946: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Co-authored-by: xixirangrang <[email protected]>
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
/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 |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
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?