Adding documentation for azure.cosmos.spark package and managing spark libraries #1013
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
jainr
added
the
safe to test
jainr
requested review from
blrchen,
edwincheung,
mufajjul,
windoze,
xiaoyongzhu and
Yuqing-cat
xiaoyongzhu
previously approved these changes
Jan 27, 2023
mufajjul
approved these changes
Jan 27, 2023
edwincheung
approved these changes
Jan 27, 2023
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.
Description
Adding documentation describing how to manage libraries from Maven, PyPi etc. on Spark Platforms in Azure i.e. Databricks and Synapse.
Also adding a note about azure.cosmos.spark package as that is not working despite being part of the gradle depedency and need to be installed explicitly on databricks. This will be needed by someone wanting to use CosmosDB as online store.
Resolves #1006
How was this PR tested?
Installed the library manually on Databricks cluster and it worked.
Does this PR introduce any user-facing changes?