Table of Contents

Search

  1. Preface
  2. Part 1: Introduction to Google BigQuery connectors
  3. Part 2: Data Integration with Google BigQuery V2 Connector
  4. Part 3: Data Integration with Google BigQuery Connector

Google BigQuery Connectors

Google BigQuery Connectors

SQL ELT optimization types

SQL ELT optimization
types

When you apply
SQL ELT optimization
, the task pushes transformation logic to the source or target database based on the optimization type you specify in the task properties.
Data Integration
translates the transformation logic into SQL queries or Google BigQuery commands to the Google BigQuery database. The database runs the SQL queries or Google BigQuery commands to process the transformations.
You can configure the following types of
SQL ELT optimization
in a
mapping
:
Full
Data Integration
first pushes as much of the transformation logic as possible to process in the target database. If the target database cannot process some of the transformation logic, it pushes that logic for processing to the source database.
Data Integration
processes all the remaining transformation logic that it cannot push to the target or source database. This is applicable for mappings that read from or write to Google BigQuery.
When you select full
SQL ELT optimization
for mappings that read from Google Cloud Storage and write to Google BigQuery,
Data Integration
pushes as much of the transformation logic as possible to process in the target database.
Data Integration
processes all the transformation logic that it cannot push to the target database.
Source
Data Integration
pushes down as much as the transformation logic as possible to process in the source database.
When you select source
SQL ELT optimization
,
Data Integration
pushes the transformation logic for all the supported transformations downstream in the mapping, but excludes the target transformation.

0 COMMENTS

We’d like to hear from you!