Google BigQuery (Beta)

Supported Versions

Latest

Driver

URL format	`jdbc:bigquery://https://www.googleapis.com/bigquery/v2:443;ProjectId=project_id;OAuthType=0;OAuthServiceAcctEmail=service_account_name;OAuthPvtKeyPath=path_to_key;`
SSL support	No
Maven Central coordinates	None. The Simba driver is available for download here
Supported versions	-
Default Java class	`com.simba.googlebigquery.jdbc42.Driver`

Using MigrateDB with Google BigQuery

Installing dependencies

Google BigQuery requires a number of dependencies to be installed manually.

Go to Google’s documentation and download the JDBC driver.

You will get a zip archive with many JARs inside.

If you are using the MigrateDB command-line, you will need to extract the contents of this archive into the migratedb/drivers/ folder.

If you are using the MigrateDB Maven plugin, you will need to add the contents of this archive to your classpath.

Configuring MigrateDB

This is a JDBC URL that points to your database. You can configure a connection using this sample URL as an example:

jdbc:bigquery://https://www.googleapis.com/bigquery/v2:443;ProjectId=<project_id>;OAuthType=0;OAuthServiceAcctEmail=<service_account_name>;OAuthPvtKeyPath=<path_to_service_account>;

We need to fetch three things to complete this URL:

project_id
service_account_name
path_to_service_account

project_id is the name of your BigQuery project within GCP.

To get service_account_name and path_to_service_account, you’ll need to create a ‘service account’ for your MigrateDB connections.

To do this, open IAM within GCP project settings. There you can create a service account. Upon creating this, you will be given the service_account_name (it will look like something@projectname.iam.gserviceaccount.com). Upon creating this you’ll have the option to download a keyfile.

The keyfile file needs to be accessible to MigrateDB, so save it somewhere accessible on your machine. Then configure path_to_service_account to point to this file.

You can learn more about service accounts here.

Set this URL in the url property in your MigrateDB configuration.

Other configuration

Set the schemas property in your MigrateDB configuration to the name of a data set within your BigQuery project. Set the user and password properties to empty in your MigrateDB configuration since we’re authenticating using the JDBC URL i.e.

migratedb.schemas=<your data set>
migratedb.user=
migratedb.password=

In a MigrateDB configuration file.

Limitations

While the Simba JDBC driver supports a number of different modes for authentication, Google User Account authentication (that is, OAuthType=1) is not recommended for desktop use and is not supported at all for unattended use, or use in Docker, as it requires a browser to be available to get an access token interactively.