Skip to content
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

Add query parameters and check for mysql kill processId #33274

Merged
merged 4 commits into from
Oct 17, 2024

Conversation

FlyingZC
Copy link
Member

Fixes #ISSUSE_ID.

Changes proposed in this pull request:


Before committing this PR, I'm sure that I have checked the following options:

  • My code follows the code of conduct of this project.
  • I have self-reviewed the commit code.
  • I have (or in comment I request) added corresponding labels for the pull request.
  • I have passed maven check locally : ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
  • I have made corresponding changes to the documentation.
  • I have added corresponding unit tests for my changes.

@FlyingZC FlyingZC self-assigned this Oct 17, 2024
@FlyingZC FlyingZC added this to the 5.5.2 milestone Oct 17, 2024
@FlyingZC FlyingZC changed the title Support mysql kill query processId Add query parameters and check for mysql kill processId Oct 17, 2024
Copy link
Member

@strongduanmu strongduanmu left a comment

Choose a reason for hiding this comment

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

Looks great, merged.

@FlyingZC FlyingZC merged commit b5d0294 into apache:master Oct 17, 2024
17 of 18 checks passed
@FlyingZC FlyingZC deleted the dev1017-kill branch October 17, 2024 06:00
RaigorJiang pushed a commit that referenced this pull request Oct 22, 2024
* Support mysql kill query processId

* Support mysql kill query processId

* Support mysql kill query processId

* Support mysql kill query processId

(cherry picked from commit b5d0294)
jiangML pushed a commit that referenced this pull request Nov 12, 2024
* Pick 5.5.0-fix #15, optimize the rollback strategy for import database config failed

* Pick #33248, Check weight load balancer props when create readwrite-splitting rule

* Pick #33274, Add query parameters and check for mysql kill processId

* Pick #33367, Remove ShardingRouteAlgorithmException check logic temporarily to support different actual table name config

* Pick #33346, Fix missing logic db when query information_schema.SCHEMATA with NOT IN clause

* Pick #33370, Fix table does not exist exception when use HintManager#setDatabaseName to transparent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants