Databricks: fix test_connection implementation #25114
Merged
Conversation
This file contains 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
|
static check fails at |
potiuk
approved these changes
Jul 18, 2022
Original implementation has used the API that exists only on AWS, so it will be failing on Azure & GCP Databricks. This PR uses another API that is available on all Databricks cloud platforms.
potiuk
force-pushed
the
databricks-fix-test-connection
branch
from
73f449e
to
a62030d
Compare
|
Rebased to account for static checks failing with new markdown-lint. |
This was referenced Aug 10, 2022
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.
Original implementation has used the API that exists only on AWS, so it will be failing on
Azure & GCP Databricks. This PR uses another API that is available on all Databricks
cloud platforms.
related: #24617