SSH: initialize Databricks Connect session in serverless mode#4590
Merged
SSH: initialize Databricks Connect session in serverless mode#4590
Conversation
ilia-db
requested review from
andrewnester,
anton-107,
denik,
pietern and
shreyas-goenka
as code owners
ilia-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
Collaborator
|
Commit: 989a84d
17 interesting tests: 7 KNOWN, 7 SKIP, 3 flaky
Top 20 slowest tests (at least 2 minutes):
|
ilia-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
andrewnester
approved these changes
Feb 25, 2026
anton-107
approved these changes
Feb 25, 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
4 participants
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.
Changes
Init spark session with databricks connect on serverless, instead of using user_namespace_initializer (which doesn't work there).
Why
Databricks connect session will ensure that all spark workloads go through spark connect router and end up on interactive spark compute
Tests
Existing tests, plus manually on both dedicated clusters and SGC