Setting Up a Native BigQuery Connection

Highlights

• In order to successfully use the native driver will require permission changes to Accelerator for a particular data set
• Users can still use the existing JDBC BigQuery Connections

Field Definitions

• Project ID: Billable Project where Accelerator will process the Query
• Target Data Set: Where Accelerator should create and destroy tables to store query results. Accelerator will elevated permissions to access this
• Bucket/Path: Location where to store exported results. This is where the temp table will be exported to be used in extraction processing
• Credentials: JSON blob for authentication to Project and GCS Location, if empty Accelerator will use the environment credentials
• Location: Server location of the GCS bucket

Permissions and Roles in Google Cloud

Customers using Accelerator with BigQuery would need to ensure that the service account that Accelerator uses has the following permissions to the target dataset where Accelerator will store query results:

bigquery.datasets.get

bigquery.tables.create

bigquery.tables.delete

bigquery.tables.export

The role roles/bigquery.dataEditor configures all of these permissions.

Accelerator would need these permissions to the source dataset where the customer's data is stored:

bigquery.tables.get

bigquery.tables.getData

The role roles/bigquery.dataViewer is the best match for the needed permissions.

Accelerator would need these permissions to the target GCS bucket where it will export the query results:

storage.objects.create

storage.objects.delete

storage.objects.get

storage.objects.list

The role roles/storage.objectAdmin is the closest match to these permissions.