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

Rules and guidelines for mappings that read from Google Cloud Storage V2 source

Rules and guidelines for mappings that read from Google Cloud Storage V2 source

Use the following rules and guidelines when you configure
SQL ELT optimization
in a mapping that reads from a Google Cloud Storage V2 source and writes to a Google BigQuery target:
  • The source fields must start with a letter or an underscore and can contain letters, numbers, and underscores up to a maximum of 300 characters. You cannot read source fields with special characters.
  • When you read a boolean integer column and write to a boolean string column in a mapping, the mapping fails.
  • When you write data with the Numeric data types to a Google BigQuery target created at runtime, where the source column has precision greater than 28, the mapping runs without
    SQL ELT optimization
    .
  • When you set the JVM option system property for the DTM type to
    -DHonorInfaDateFormat=true
    for the Secure Agent and configure a mapping with
    SQL ELT optimization
    , the mapping fails with the following error if it reads the date data type that is not in the YYYY-MM-DD format:
    The Secure Agent failed to run the full SQL ELT query due to the following error: [Failed to parse input string "1972-12-31"]
  • When you map a string data type in the source to a time data type in the target, and the data is in the format HH24:MI:SS.US, the mapping fails with the following error:
    [Invalid timestamp: '00:00:00.000001']

0 COMMENTS

We’d like to hear from you!