Google BigQuery as a source
You can create a data pipeline that loads data from Google BigQuery to a destination. To provide the information SnapLogic® AutoSync needs to connect to Google BigQuery, supply new credentials in the wizard or select saved credentials. The create credentials page explains how to create credentials in the AutoSync wizard.
Supported Account types
The IIP provides multiple Account types for most endpoints and not all types are compatible with AutoSync. When you create or edit a data pipeline, the existing credentials list only includes compatible Accounts. AutoSync supports the following IIP Account types:
- Google BigQuery OAuth2
- When loading data from a Google BigQuery source to a Google BigQuery destination, the source schema must be different than the destination schema.
- When using BigQuery as both a source and a target, the loaded data for some columns might be a different data type than they were in the source. This is because AutoSync maps data through a common data model.
Google BigQuery properties include the following:
- Credential label: A unique, meaningful name such as
Sales-Shared-BigQuery. If a configuration with the same name exists, AutoSync displays an
Asset conflict error message.
- Authorize: This button authorizes AutoSync with your Google account.
- Share: (Optional) Select a user group to share this configuration with. Environment admins (formerly Org admins) create user groups to share credentials. If you are a member of a user group, you can select it from the dropdown. You can also select the global shared folder, which shares the credentials with everyone in your Org.
- Validate and Save: After saving and validating, AutoSync adds the configuration to the list of saved credentials.
- Enter Project ID: Enter the ID of the BigQuery Project to load data into.
- Select schema: AutoSync populates this list from the account. Choose the schema to use as the destination.
- Location: (Optional) If you are using a single region dataset, you can select the region in the Location field. If you are using a multi-region dataset, you can leave this field blank.