Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange for Google BigQuery
  3. PowerExchange for Google BigQuery Configuration
  4. Configuring HTTP Proxy Options
  5. Google BigQuery Connections
  6. PowerExchange for Google BigQuery Data Objects
  7. PowerExchange for Google BigQuery Mappings
  8. Google BigQuery Lookup
  9. Google BigQuery Run-Time Processing
  10. Appendix A: Google BigQuery Data Type Reference

PowerExchange for Google BigQuery User Guide

PowerExchange for Google BigQuery User Guide

Rules and Guidelines for PowerExchange for Google BigQuery Data Object Operations

Rules and Guidelines for PowerExchange for Google BigQuery Data Object Operations

Use the following rules and guidelines when you configure a PowerExchange for Google BigQuery data object read and write operation:
  • You must define a primary key in the source table and target table for update and delete operations.
    If you do not define a primary key in the target table, the mapping fails to update records in or delete records from the target table.
  • You cannot read hierarchical data from a Google BigQuery source, convert the hierarchical input to relational output, and write data to relational targets.
  • You cannot perform more than one operation with a pre SQL or post SQL command.
  • If you perform an UPDATE or DELETE operation with a pre SQL or post SQL command, you must specify the following parameter in the pre SQL configuration or post SQL configuration:
    UseLegacySQL:False
  • To perform an upsert operation on a column, you must ensure that the column in the target table is set to Required in Google BigQuery.
  • When you perform an upsert operation on a Google BigQuery target table, you cannot perform an update operation on multiple rows.
  • When you configure a Google BigQuery connection in simple mode, you can perform upsert operation on columns of primitive data types only.
  • When you import a Google BigQuery partitioned table for the data object read operation or write operation, you must use a Google BigQuery connection in hybrid mode.
  • When you configure an uncached lookup operation to look up data from a Google BigQuery source, ensure that you do not select
    Direct
    for the Read Mode property. Otherwise, the mapping fails.
  • When you configure an uncached lookup operation to look up data from a Google BigQuery source, ensure that you do not set the
    Number of Rows to Read
    property to a non-zero value. Otherwise, the mapping fails.
  • When you configure an uncached lookup operation to look up data from a Google BigQuery source, ensure that you do not set the
    On multiple matches
    property to
    Return Any
    . Otherwise, the mapping fails.
  • When you configure an uncached lookup operation to look up data from a Google BigQuery source, ensure that you do not configure the
    SQL Override Query
    property. Otherwise, the mapping fails.

0 COMMENTS

We’d like to hear from you!