Skip to content

dumpling: New terminology for MySQL#57188

Merged
ti-chi-bot[bot] merged 10 commits intopingcap:masterfrom
dveeden:mysqlNewTerm
Nov 7, 2024
Merged

dumpling: New terminology for MySQL#57188
ti-chi-bot[bot] merged 10 commits intopingcap:masterfrom
dveeden:mysqlNewTerm

Conversation

@dveeden
Copy link
Contributor

@dveeden dveeden commented Nov 6, 2024

What problem does this PR solve?

Issue Number: close #53082

Problem Summary:

What changed and how does it work?

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No need to test
    • I checked and no code files have been changed.

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Dumpling now supports dumpling databases from MySQL 8.4 and newer

@dveeden dveeden requested review from glorv and lance6716 November 6, 2024 19:39
@ti-chi-bot ti-chi-bot bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. component/dumpling This is related to Dumpling of TiDB. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Nov 6, 2024
@tiprow
Copy link

tiprow bot commented Nov 6, 2024

Hi @dveeden. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Details

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.

@codecov
Copy link

codecov bot commented Nov 6, 2024

Codecov Report

❌ Patch coverage is 38.88889% with 22 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.1986%. Comparing base (b522e98) to head (a282838).
⚠️ Report is 2723 commits behind head on master.

Additional details and impacted files
@@                Coverage Diff                @@
##             master     #57188         +/-   ##
=================================================
- Coverage   73.0639%   56.1986%   -16.8653%     
=================================================
  Files          1659       1785        +126     
  Lines        458021     638209     +180188     
=================================================
+ Hits         334648     358665      +24017     
- Misses       102834     255262     +152428     
- Partials      20539      24282       +3743     
Flag Coverage Δ
integration 48.8079% <ø> (?)
unit 72.4929% <38.8888%> (-0.2229%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
dumpling ∅ <38.8888%> (∅)
parser ∅ <ø> (∅)
br 51.7128% <ø> (+5.1281%) ⬆️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dveeden dveeden requested review from GMHDBJD and tangenta November 6, 2024 20:00
Copy link
Contributor

@lance6716 lance6716 left a comment

Choose a reason for hiding this comment

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

/hold

free to unhold

@ti-chi-bot ti-chi-bot bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Nov 7, 2024
@lance6716
Copy link
Contributor

Maybe CI is also needed to be changed

++(dumpling/tests/consistency/run.sh:29): run_sql 'show master status;'
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'master status' at line 1

@ti-chi-bot ti-chi-bot bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Nov 7, 2024
@dveeden
Copy link
Contributor Author

dveeden commented Nov 7, 2024

Maybe CI is also needed to be changed

++(dumpling/tests/consistency/run.sh:29): run_sql 'show master status;'
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'master status' at line 1

Yes indeed. Trying to fix this in 2343947 but I'm not very familiar with how this test setup works

@dveeden
Copy link
Contributor Author

dveeden commented Nov 7, 2024

/ok-to-test

@ti-chi-bot ti-chi-bot bot added the ok-to-test Indicates a PR is ready to be tested. label Nov 7, 2024
@lance6716
Copy link
Contributor

/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 Nov 7, 2024
@dveeden
Copy link
Contributor Author

dveeden commented Nov 7, 2024

/retest

1 similar comment
@dveeden
Copy link
Contributor Author

dveeden commented Nov 7, 2024

/retest

Copy link
Contributor

@GMHDBJD GMHDBJD left a comment

Choose a reason for hiding this comment

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

LGTM

@ti-chi-bot
Copy link

ti-chi-bot bot commented Nov 7, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: GMHDBJD, lance6716

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 lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Nov 7, 2024
@ti-chi-bot
Copy link

ti-chi-bot bot commented Nov 7, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-11-07 02:19:12.241412523 +0000 UTC m=+1093865.080568069: ☑️ agreed by lance6716.
  • 2024-11-07 11:49:38.214790652 +0000 UTC m=+1128091.053946195: ☑️ agreed by GMHDBJD.

@ti-chi-bot ti-chi-bot bot merged commit 6abe4fe into pingcap:master Nov 7, 2024
dveeden added a commit to dveeden/tidb that referenced this pull request Dec 18, 2025
@ti-chi-bot ti-chi-bot bot added the needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. label Mar 10, 2026
@ti-chi-bot
Copy link
Member

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

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

Labels

approved component/dumpling This is related to Dumpling of TiDB. lgtm needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. ok-to-test Indicates a PR is ready to be tested. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dumpling: Support for MySQL 8.4.0

4 participants