Skip to content

v8.5.6: DM supports MySQL 8.4#22505

Merged
ti-chi-bot[bot] merged 3 commits intopingcap:masterfrom
dveeden:dm_mysql84
Apr 1, 2026
Merged

v8.5.6: DM supports MySQL 8.4#22505
ti-chi-bot[bot] merged 3 commits intopingcap:masterfrom
dveeden:dm_mysql84

Conversation

@dveeden
Copy link
Copy Markdown
Contributor

@dveeden dveeden commented Feb 26, 2026

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.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @dveeden, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the DM compatibility catalog to accurately reflect the current support status for MySQL 8.4. The documentation now indicates that MySQL 8.4 is in an 'Experimental' state, providing users with the latest information regarding its integration capabilities with DM.

Highlights

  • MySQL 8.4 Compatibility Update: The compatibility status for MySQL 8.4 with DM has been updated from 'Incompatible' to 'Experimental' in the documentation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • dm/dm-compatibility-catalog.md
    • Updated the compatibility status for MySQL 8.4 from 'Incompatible' to 'Experimental'.
Activity
  • The author signed the Contributor License Agreement.
  • The changes are marked to apply to the master, v9.0, and v8.5 branches.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@ti-chi-bot ti-chi-bot bot added missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 26, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the compatibility status for MySQL 8.4 with TiDB Data Migration (DM) to 'Experimental'. My review focuses on documentation formatting and consistency. I've identified a minor formatting issue in the markdown table and provided a suggestion to correct it for better readability and to align with the rest of the document.

| MySQL 8.0 | GA | Does not support binlog transaction compression [Transaction_payload_event](https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html). |
| MySQL 8.1 ~ 8.3 | Not tested | |
| MySQL 8.4 | Incompatible | For more information, see [DM Issue #11020](https://github.com/pingcap/tiflow/issues/11020). |
| MySQL 8.4 | Experimental|
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

To maintain correct and consistent markdown table formatting, please add spaces around the Experimental value and ensure the row has the correct number of columns by adding a final pipe.

Suggested change
| MySQL 8.4 | Experimental|
| MySQL 8.4 | Experimental | |
References
  1. The repository style guide requires correct formatting and consistency in documentation. This change ensures the markdown table is well-formed and readable, consistent with other entries. (link)

@Oreoxmt Oreoxmt self-assigned this Feb 27, 2026
@Oreoxmt Oreoxmt added the translation/doing This PR's assignee is translating this PR. label Feb 27, 2026
@ti-chi-bot ti-chi-bot bot removed the missing-translation-status This PR does not have translation status info. label Feb 27, 2026
@Oreoxmt Oreoxmt self-requested a review February 27, 2026 02:02
@Oreoxmt Oreoxmt added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. labels Mar 4, 2026
Copy link
Copy Markdown
Collaborator

@Oreoxmt Oreoxmt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM

@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Mar 9, 2026
@Oreoxmt Oreoxmt changed the title DM: MySQL 8.4 support is now available v8.5.6: DM supports MySQL 8.4 Mar 9, 2026
@Oreoxmt Oreoxmt added translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. and removed translation/doing This PR's assignee is translating this PR. labels Mar 9, 2026
@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Mar 17, 2026

@Oreoxmt: Your lgtm message is repeated, so it is ignored.

Details

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.

@Oreoxmt
Copy link
Copy Markdown
Collaborator

Oreoxmt commented Mar 17, 2026

/cc @alastori @OliverS929

@ti-chi-bot ti-chi-bot bot requested a review from alastori March 17, 2026 03:45
@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Mar 17, 2026

@Oreoxmt: GitHub didn't allow me to request PR reviews from the following users: OliverS929.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @alastori @OliverS929

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.

@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Mar 19, 2026

@alastori: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

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.

@Oreoxmt
Copy link
Copy Markdown
Collaborator

Oreoxmt commented Mar 30, 2026

/cc @qiancai

@ti-chi-bot ti-chi-bot bot requested a review from qiancai March 30, 2026 02:54
@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Mar 30, 2026
@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Mar 30, 2026

[LGTM Timeline notifier]

Timeline:

  • 2026-03-09 04:06:07.719686049 +0000 UTC m=+236599.231743700: ☑️ agreed by Oreoxmt.
  • 2026-03-30 07:19:58.030650702 +0000 UTC m=+163203.236010759: ☑️ agreed by qiancai.

@Oreoxmt
Copy link
Copy Markdown
Collaborator

Oreoxmt commented Apr 1, 2026

/approve

@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Apr 1, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Oreoxmt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the approved label Apr 1, 2026
@Oreoxmt
Copy link
Copy Markdown
Collaborator

Oreoxmt commented Apr 1, 2026

/unhold

@ti-chi-bot ti-chi-bot bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 1, 2026
@ti-chi-bot ti-chi-bot bot merged commit 6cce8a1 into pingcap:master Apr 1, 2026
12 checks passed
@ti-chi-bot
Copy link
Copy Markdown
Member

In response to a cherrypick label: new pull request created to branch release-8.5: #22676.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants