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

Clean stop a SQL ELT optimization job

Clean stop a
SQL ELT optimization
job

When a task enabled for
SQL ELT optimization
is running, you can clean stop the job to terminate all the issued statements and processes spawned by the job.
You can use this option for mappings enabled for
SQL ELT optimization
that use the Google BigQuery V2 connection either in the source or target transformation, or both.
Use the
Clean Stop
option on the My Jobs page in Data Integration and the All Jobs and Running Jobs page in Monitor.
See the following exceptions before you clean stop a
SQL ELT optimization
task:
  • When you clean stop a task enabled for source
    SQL ELT optimization
    that reads from or writes to Google BigQuery and the target or source properties in the mapping contains pre-SQL or post-SQL statements, even if the select query is terminated, the job continues to run the target post-SQL query.
  • When you start a job enabled for full
    SQL ELT optimization
    and clean stop it immediately, and if the mapping is configured to create a new target at runtime, the table is created even if the job is terminated.

0 COMMENTS

We’d like to hear from you!