Databricks & Bigquery

[BabuMahesh]

Databricks is packaging a old version of big-query jar(Databricks also repackaged and created a fat jar), and our application needs a latest jar. Now the latest jar depends on spark-bigquery-connector.properties  file for a property scala.binary.version, this property is not available on old version of jars.

As databricks runtime is always loading the internal packaged jars first, its own property file is loaded too.

While Our code(The latest bigquery jar internal) looks for the specific property (scala.binary.version), its not available and app fails to start. Any suggestion to overcome this.

As a workaround,

1. Relocated the all the bigquery classes (We cant relocate the internally referenced properties files path )

2. Removed the class file from bigquery jar which does this property check and added our own class implementaion and bundled back to application fat jar 

 

[Kaniz_Fatma]

Hi @BabuMahesh, It seems like you’re dealing with a complex issue related to jar conflicts in Databricks. 

Here are a few suggestions that might help:

Uninstall the old jars from the cluster: Continually push new changes in subsequent versions with sm.... This approach might require you to delete the old jars from dbfs:/FileStore/jars/* and restart the c....

Change the classpath manually and build the jar with a different groupId using Maven: This can help ....

Use a try-finally block in your code: This can ensure that the clean-up method is called, which migh...s.

Explicitly set the project ID in your code when loading data from BigQuery to Databricks: This can h....