When setting up direct data distribution from your BigQuery data warehouse, pay attention to the best practices concerning the following:
- Output stage prefixes
- User access rights
- Data types
This article is applicable to all use cases of GoodData and BigQuery integration:
- Load Sample Data from BigQuery into GoodData
- Load Your Own BigQuery Data into GoodData Workspace
- Integrate Data Warehouses Directly to GoodData based on an Existing LDM
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.
User Access Rights
For the minimum sufficient level of access, your BigQuery service account must have the
bigquery.jobUser roles assigned (for more information, see https://cloud.google.com/iam/docs/service-accounts and https://cloud.google.com/bigquery/docs/access-control).
Specifically, your BigQuery service account must have the following permissions:
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 Type||GoodData LDM Data Type|
|FLOAT64||DECIMAL (12, 2)|
|NUMERIC||DECIMAL (12, 2)|