Repository navigation
Preserve JDBC session diagnostics in 1.3 - #19115
Merged
Merged
Conversation
* Preserve JDBC legacy-server diagnostics across locales * Handle JDBC session diagnostics across locales and absent messages * Declare logback-core for JDBC test dependencies * Test JDBC diagnostics without logging dependencies (cherry picked from commit e09005e)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backports the JDBC session-open failure handling from source commit
e09005e87d036d308676a2c7a879898a9f231329todev/1.3. The change recognizes the legacyclient_protocoldiagnostic and safely handles absent Thrift exception messages while retaining the existing connection error format. Tests cover the legacy protocol diagnostic, a different missing-field diagnostic, and a message-less transport exception. The password-expiration warning portion of the source commit is omitted because its supporting capability is not present on the target branch. Local validation passed: the clean JDBC reactor test, includingIoTDBConnectionTest(8/8), Spotless, Checkstyle, and main/test compilation. A remote validation attempt stopped during GitHub TLS negotiation before Maven started.