[SPARK-53260][SQL] Reducing number of JDBC overhead connections creation #51991
Conversation
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
vanja-vujovic-db
force-pushed
the
connections
branch
from
6b58f79 to
62c44e2
Compare
|
Let's file a JIRA and add it to the PR title. |
vanja-vujovic-db
changed the title
cloud-fan
approved these changes
Aug 20, 2025
cloud-fan
changed the title
|
thanks, merging to master! |
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 changes were proposed in this pull request?
JDBC connectors open more connections to remote engines than needed. After logging the results, from 2-4 connections open up while doing a sql(...) command. The 2 connections always invoked both come from JDBCTableCatalog, so connection sharing between those 2 is created.
Why are the changes needed?
To reduce query time.
Does this PR introduce any user-facing change?
How was this patch tested?
Locally.
Was this patch authored or co-authored using generative AI tooling?