Adding azure-cosmos-package to databricks spark config#972
Merged
jainr merged 3 commits intofeathr-ai:mainfrom Jan 19, 2023
Merged
Adding azure-cosmos-package to databricks spark config#972jainr merged 3 commits intofeathr-ai:mainfrom
jainr merged 3 commits intofeathr-ai:mainfrom
Conversation
…able on the cluster
xiaoyongzhu
approved these changes
Jan 19, 2023
Member
|
I think this PR should be ready as long as the cosmos error is gone. Other failures can be safely ignored. |
Yuqing-cat
approved these changes
Jan 19, 2023
Collaborator
Yuqing-cat
left a comment
There was a problem hiding this comment.
The change looks good to me. Let's wait and see if the cosmos failure in CI result is gone.
xiaoyongzhu
pushed a commit
that referenced
this pull request
Jan 20, 2023
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.
Adding azue.spark.cosmos package to spark config so it is available to databricks test cluster.
Does this PR introduce any user-facing changes?