MilanTyagi2004 opened a new pull request, #37472:
URL: https://github.com/apache/shardingsphere/pull/37472
Fixes #37404
Changes proposed in this pull request:
- In Apache ShardingSphere Proxy using the MySQL protocol, cancelling a
running SQL statement does not correctly interrupt
the underlying JDBC Statement in a cluster environment.
- Although a Process instance is created for the execution, the MySQL thread
ID is not bound to the connection session. As a
result, KILL QUERY / Statement.cancel() cannot locate or terminate the
actual running MySQL query.
- This pull request binds the MySQL thread ID to the connection session
after authentication, ensuring that cancellation signals
are correctly propagated to the JDBC layer.
Expected behavior
- Statement.cancel() or KILL QUERY should terminate the running MySQL query.
Actual behavior
- The query continues running even after cancellation is requested.
Environment
- ShardingSphere version: 5.5.3-SNAPSHOT
- OS: Windows 11
- Database: MySQL
- Mode: Cluster mode
---
Before committing this PR, I'm sure that I have checked the following
options:
- [x] My code follows the [code of
conduct](https://shardingsphere.apache.org/community/en/involved/conduct/code/)
of this project.
- [x] I have self-reviewed the commit code.
- [x] I have (or in comment I request) added corresponding labels for the
pull request.
- [x] I have verified the changes locally with Maven (module-level and
targeted builds)..
- [ ] I have made corresponding changes to the documentation.
- [ ] I have added corresponding unit tests for my changes.
- [ ] I have updated the Release Notes of the current development version.
For more details, see [Update Release
Note](https://shardingsphere.apache.org/community/en/involved/contribute/contributor/)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
