issue-6044: Updating Databricks API endpoints to appropriate versions
#60647
+28
−28
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.
Description
As part of #59217, certain endpoints we improperly updated to version
2.2when they, in fact, did not support that endpoint. This was the case for the.../sql/endpoints, which are called out in #60444. Each of the Databricks endpoints were researched to find the latest supported version. From there, the provider was appropriately updated.issue-59189:Updating Databricks provider to point to2.2/jobs/...endpoint #59217Testing
The appropriate unit-tests have been updated. These were run using the command below.
breeze testing providers-tests --test-type "Providers[databricks]"Was generative AI tooling used to co-author this PR?