GoodData-BigQuery Integration Details

When setting up direct data distribution from your BigQuery data warehouse, pay attention to the considerations and best practices listed in this article.

This article is applicable to all use cases of GoodData and BigQuery integration:

User Access Rights

To connect your BigQuery data warehouse and GoodData, we recommend that you use Google Cloud Platform service account.

For the sufficient level of access, grant your service account the following user roles:

  • bigquery.dataViewer
  • bigquery.jobUser

For more information, see and

Your service account must have the following permissions:

  • bigquery.tables.get
  • bigquery.tables.getData
  • bigquery.tables.list

Google Service Account Key File

GoodData supports using Google service account key file to integrate your BigQuery project with the GoodData workspace and create a Data Source. For more information, see Create a Data Source.

The file is used to import most of the settings when you establish the connection between your BigQuery project and GoodData. The following information is extracted:

  • client email
  • private key
  • Google project ID

To learn how to create service account key files, see

Data Types

The BigQuery data warehouse provides a wide range of data types. During mapping the BigQuery schema and the GoodData logical data model (LDM), data types are automatically converted from a BigQuery data type to a GoodData LDM data type. Some columns may be ignored because their data type is not supported within GoodData or their type may lead to performance issues. If you want to prevent automatic changes, update the schema manually.

BigQuery Data TypeGoodData LDM Data Type
ARRAYNot supported
BYTESNot supported
GEOGRAPHYNot supported
STRUCTNot supported
TIMENot supported

Materialized Views

Materialized views are supported. They appear in the list of available tables in the LDM Modeler alongside regular tables or views and are included in the schema scanning.

Output Stage Prefixes

BigQuery does not support primary key constraints for tables. After generating the Output Stage, manually rename the a__ prefix to either cp__ (connection point) or r__ (reference) for the generated views.