-
Notifications
You must be signed in to change notification settings - Fork 327
Fix for using Broadcast variables in Databricks #766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for using Broadcast variables in Databricks #766
Conversation
merging latest from master
Merging latest from master
Yes, can you update the description with the DB runtime you tested against? |
@Niharikadutta Can you also test with DB runtime 7.X (Spark 3.0)? |
…adutta/spark into nidutta/databricks_broadcast_fix
@imback82 Tested with DB runtime 7.3 LTS as well. |
Maven build is failing on Ubuntu with the following error:
|
@imback82 , @suhsteve , @elvaliuliuliu Could you please review this PR? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as well (one nit comment), thanks @Niharikadutta!
Co-authored-by: Terry Kim <yuminkim@gmail.com>
This PR changes how
setupBroadcast
is called for Databricks Environment, by passingjavaSparkContext
to it.Change tested against Databricks Runtime version 6.6 and 7.3.
Fixes #754