The Google BigQuery component allows you to connect systems to BigQuery, enabling data ingestion.
IMPORTANTThe Google BigQuery component works exclusively as a producer (connector), which means it does not allow querying BigQuery, only inserting data.
URI Syntax: google-bigquery:projectId:datasetId:tableId
Path parameters
Name | Description | Default | Type |
|---|---|---|---|
projectId (common) | (required) Project ID in Google Cloud. | — | String |
datasetId (common) | (required) Dataset ID in BigQuery. | — | String |
tableId (common) | Table ID in BigQuery. | — | String |
Query parameters
Name | Description | Default | Type |
|---|---|---|---|
serviceAccountKey (security) | Service account key in JSON format to authenticate an application as a service account on Google Cloud Platform. | — | String |
IMPORTANTBefore running the integration flow, import the Google Cloud service account key to a config map. This key will be used as a resource in the integration:
The "key.json" file contains the service account credentials in JSON format. In Integrations, this key will be configured as a Resource file.
Read more about Resources files.
The flow below receives data through a POST request, processes the information, and sends it to Google BigQuery, performing the necessary conversions to JSON format during execution:
The flow starts with a POST request in the /demo endpoint.
The received data is converted from JSON (unmarshal) to an internal format using the Jackson library.
The data is sent to Google BigQuery:
employeespoc_bigqueryregistry-ipaas-testingkey.json.The data is converted again (marshal) to JSON format using the Jackson library, after processing.
NOTEThe Google BigQuery component receives a "List" or "Map" as input, which makes it necessary to use the "unmarshal" EIP to convert the data to the appropriate format.

Sending a request with 1 element:
Sending a request with 1 array:
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more