Connections > Google BigQuery V2 connection properties > Connect to Google BigQuery
  

Connect to Google BigQuery

Let's configure the Google BigQuery V2 connection properties to connect to Google BigQuery.

Before you begin

Before you configure a Service Account connection, download the Google service account key file in JSON format. The service account key file is created when you create a Google service account. The key file contains the client email, private key, and project ID that you use to create a Service Account connection.
The following video shows you how to get the information you need from your Google BigQuery account:
https://infa.media/3e4LzdW
For information about the Workload Identity Federation prerequisites, see the following topics:

Connection details

The following table describes the basic connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
This property is not supported by Data Ingestion and Replication and the Data Access Management services.
When you enable the secret vault in the connection, you can select the credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note:
If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
For information about how to configure and use a secrets manager, see "Secrets manager configuration" in the Administrator help.
Runtime Environment
The name of the runtime environment where you want to run tasks.
Select a Secure Agent, Hosted Agent, or serverless runtime environment.
For application ingestion and replication tasks and database ingestion and replication tasks, you can use a Secure Agent or serverless runtime environment. The tasks must have a source type supported for serverless use. You cannot run an application ingestion and replication task, database ingestion and replication task, file ingestion or replication task, or streaming ingestion and replication task on a Hosted Agent or elastic runtime environment.
For more information about runtime environments, see Runtime Environments in the Administrator help.

Authentication types

Google BigQuery V2 Connector connects to Google BigQuery with a service account key or with Workload Identity Federation (WIF).
Select one of the following authentication types in the connection:
Authentication type
Description
Service Account
Authenticate with the credentials in a Google service account key file.
WIF (Authorization Code)
Authenticate with WIF and an identity provider that uses the OAuth 2.0 authorization code grant. You sign in to the identity provider to generate an access token.
You can configure Okta as the identity provider.
WIF (Client Credentials)
Authenticate with WIF and an identity provider that uses the OAuth 2.0 client credentials grant. The connection doesn't require a user to sign in. You can also impersonate a service account and access datasets in a different project.
You can configure Microsoft Entra ID as the identity provider.
Select the required authentication type and configure the authentication-specific parameters.
Default is Service Account authentication type.

Connection retry

The following table describes the properties for connection retry:
Property
Description
Enable Retry¹
Select this option if you want the Secure Agent to attempt a retry to receive the response from the Google BigQuery endpoint.
For more information about the errors for which the connector can attempt a retry, see Error messages in the Google BigQuery documentation.
You can configure the retry strategy to read data from Google BigQuery in direct or staging mode and write data to Google BigQuery in bulk mode.
The retry strategy is not applicable in the CDC and streaming modes when you write data to a Google BigQuery target.
The connection retry option also applies to a connection configured to use the proxy server to connect to the endpoint.
Default is unselected.
Maximum Retry Attempts
Appears only if you select the Enable Retry property.
The maximum number of retry attempts that the Secure Agent performs to receive the response from the Google BigQuery endpoint.
If the Secure Agent fails to connect to Google BigQuery within the maximum retry attempts, the connection fails.
Default is 6 attempts.
Initial Retry Delay
Appears only if you select the Enable Retry property.
The initial wait time in seconds before the Secure Agent attempts to retry the connection.
Default is 1 second.
Retry Delay Multiplier
Appears only if you select the Enable Retry property.
The multiplier that the Secure Agent uses to exponentially increase the wait time between successive retry attempts up to the maximum retry delay time.
Default multiplier is 2.0. You can also use fractional values.
Maximum Retry Delay
Appears only if you select the Enable Retry property.
The maximum wait time in seconds that the Secure Agent waits between successive retry attempts.
Default is 32 seconds.
Total Timeout
Appears only if you select the Enable Retry property.
The total time duration in seconds that the Secure Agent attempts to retry the connection after which the connection fails.
Default is 50 seconds.
¹ Doesn't apply to mappings in advanced mode.