Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange for Google BigQuery
  3. PowerExchange for Google BigQuery Configuration
  4. Google BigQuery Sources and Targets
  5. Google BigQuery Mappings
  6. Google BigQuery Sessions
  7. Google BigQuery as CDC Target
  8. Google BigQuery Pushdown Optimization
  9. Appendix A: Google BigQuery Data Type Reference

PowerExchange for Google BigQuery User Guide for PowerCenter

PowerExchange for Google BigQuery User Guide for PowerCenter

Google BigQuery Pushdown through ODBC Connection

Google BigQuery Pushdown through ODBC Connection

Use an ODBC connection to enable full or source pushdown optimization when you want to read data from a Google BigQuery source and write to an Google BigQuery target. The mapping logic is processed entirely in Google BigQuery.
When you run a task configured for pushdown optimization, the task converts the transformation logic to an SQL statement. The task sends the SQL statement to the database and the database executes the SQL statement.
Example
You work for a rapidly growing data science organization. Your organization develops software products to analyze financials, building financial graphs connecting people profiles, companies, jobs, advertisers, and publishers. The organization uses infrastructure based on Google Cloud Platform and stores its data in Google BigQuery, a petabyte scale data warehouse. The organization plans to implement a business intelligence service to build visualization and perform real-time analysis. Therefore, you need to port the vast amount of data stored in Google BigQuery to the business intelligence service. You can use PowerExchange for Google BigQuery to read data from Google BigQuery. To read this large amount of data, you can use source pushdown for the ODBC connection type. Using the ODBC connection type with pushdown optimization enhances the performance.

Prequisites

When you run a session for full pushdown optimization, you must have the following permissions:
  • bigquery.datasets.get
  • bigquery.datasets.getIamPolicy
  • bigquery.models.getData
  • bigquery.models.getMetadata
  • bigquery.models.list
  • bigquery.routines.get
  • bigquery.routines.list
  • bigquery.tables.create
  • bigquery.tables.delete
  • bigquery.tables.export
  • bigquery.tables.get
  • bigquery.tables.getData
  • bigquery.tables.getIamPolicy
  • bigquery.tables.list
  • resourcemanager.projects.get
  • resourcemanager.projects.list
  • bigquery.jobs.create
When you configure the
Allow Temporary View for Pushdown
in the session, you must have the bigquery.tables.create and bigquery.tables.delete to permissions create and drop views.
The dataset configured to create and drop views is used as the default dataset in the Google BigQuery ODBC driver.

0 COMMENTS

We’d like to hear from you!