Repository navigation
Conversation
Follow-up to apache#1233. Document under useEncryption that endpoint locations without TLS are refused on an encrypted connection, test that the endpoint's remaining locations are still tried, and close the handler in the test.
jbonofre
requested review from
laurentgo,
lidavidm and
wgtmac
as code owners
November 15, 2026 13:46
lidavidm
approved these changes
Nov 15, 2026
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.
What's Changed
Follow-up to #1233, which made an encrypted connection refuse endpoint locations that don't use TLS.
useEncryptionin the Flight SQL JDBC driver docs, since connections that used to fall back to plaintext now fail.verifyNoInteractions(sqlClient): it checks that the original connection isn't used instead, while the error message is what shows that no connection was attempted.Closes #1232.