Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Google BigQuery is a cloud database like system that is used mostly for querying data powered by Google Cloud Platform (GCP).

Stambia Data Integration allows to work with Google BigQuery databases to produce fully customized Integration Processes.

The database structure can be entirely reversed in Metadata and then used in Mappings and Processes to design and adapt the business rules to meet the user's requirements.

Note:

Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

If you have any question, any feature request or any issue, do not hesitate to contact us.

This component may require a dedicated license.

Please contact the Stambia support team if you have any doubt and if you need to use it in a production environment.

 

Prerequisites:

You must install Google Cloud Platform connector to be able to work with Google BigQuery.

Please refer to the following article that will guide you to accomplish this.

When the installation is completed, you can lead to this getting started article which explains how to work with Google BigQuery in Stambia.

 

Supported features

You can find below an overview of what Stambia DI can do with Google BigQuery databases

Name Description
Reverse

The database structure can be reversed in a dedicated Metadata
Google BigQuery as Target

Data can be loaded into Google BigQuery from any database, flat file, or directly from GCS.
Google BigQuery as Source The connector supports reading data from Google BigQuery to load it into another database, file, ...
Integration methods

Data can be sent to Google BigQuery with the following methods:

  • direct: data is directly sent to Google BigQuery
  • storage: data is extracted to a file which is sent to Google Storage and then loaded into Google BigQuery through Google's loader. This offers better performances on large set of data.
Storage methods

When integrating data into Google BigQuery using the storage method, you have the choice of how it should be done:

  • stream: Data is streamed directly in the Google Storage Bucket.
  • localfile: Data is first exported to a local temporary file, which is then sent to the defined Google Storage Bucket.

Depending on the amount of data sent and network quality, for instance, one method or the other can have better performances
Query Language

Stambia's Google BigQuery connector is using Standard SQL as default query mode.

All statements supported by Google BigQuery's Standard SQL can therefore be used seamlessly without any particular configuration.
Data consultation The connector supports consulting Google BigQuery data directly from the Designer.

 

 

Articles

Suggest a new Article!