Comment on page


Instructions to work with BigQuery
Zingg can seamlessly work with Google BigQuery. Please find below details about the properties that must be set.
The two driver jars namely spark-bigquery-with-dependencies_2.12-0.24.2.jar and gcs-connector-hadoop2-latest.jar are required to work with BigQuery. To include these BigQuery drivers in the classpath, please configure the runtime properties to include these.
In addition, the following property needs to be set
If Zingg is run from outside the Google cloud, it requires authentication, please set the following env variable to the location of the file containing the service account key. A service account key can be created and downloaded in JSON format from the Google Cloud console.
export GOOGLE_APPLICATION_CREDENTIALS=path to google service account key file
Connection properties for BigQuery as a data source and data sink are given below. If you are curious to know more about how Spark connects to BigQuery, you may look at the Spark BigQuery connector documentation.

Properties for reading data from BigQuery:

The property "credentialsFile" should point to the google service account key file location. This is the same path that is used to set variable GOOGLE_APPLICATION_CREDENTIALS. The "table" property should point to a BigQuery table that contains source data. The property "viewsEnabled" must be set to true only.
"data" : [{
"props": {
"credentialsFile": "/home/work/product/final/zingg-1/mynotification-46566-905cbfd2723f.json",
"table": "mynotification-46566.zinggdataset.zinggtest",
"viewsEnabled": true

Properties for writing data to BigQuery:

To write to BigQuery, a bucket needs to be created and assigned to the "temporaryGcsBucket" property.
"output" : [{
"props": {
"credentialsFile": "/home/work/product/final/zingg-1/mynotification-46566-905cbfd2723f.json",
"table": "mynotification-46566.zinggdataset.zinggOutput",


  • The library "gcs-connector-hadoop2-latest.jar" can be downloaded from Google and the library "spark-bigquery-with-dependencies_2.12-0.24.2" from the maven repo.
  • A typical service account key file looks like the below. The format of the file is JSON.
"type": "service_account",
"project_id": "mynotification-46566",
"private_key_id": "905cbfd273ff9205d1cabfe06fa6908e54534",
"private_key": "-----BEGIN PRIVATE KEY-----CERT.....",
"client_id": "11143646541283115487",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://oauth2.googleapis.com/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/zingtest%44mynotification-46566.iam.gserviceaccount.com"