When you flag rows for an insert, update, delete, or reject operation based on the data driven condition for a Google BigQuery target in a mapping, you must select the
Enable Data Driven
and
Enable Merge
properties.
Rules and Guidelines
Consider the following rules and guidelines when you perform a data driven operation on a Google BigQuery target:
You cannot parameterize the target connection or object.
You cannot use the Google BigQuery V2 connection in complex mode.
When you configure a data driven condition, ensure to map the fields involved in the condition within the field mapping.
Ensure that you do not specify a column of Record data type, repeated columns, or Record data type with repeated columns in the data driven condition.
When you use a Google BigQuery connection in simple mode, ensure that you do not specify a column of Byte, Record data type, or repeated columns in the data driven condition.
When you use a Google BigQuery connection in hybrid mode, ensure that you do not specify a column of Byte, Record data type with repeated columns, or Primitive data type with repeated columns in the data driven condition.
When you define the DD_UPDATE constant in the data driven condition, ensure that there are no null values in the update column.
When you use the DD_REJECT constant in the data driven condition to reject all the rows, ensure that you have selected the
Persist Staging File After Loading
advanced target property.
Ensure that the target table is not an external table.
When you use the Google BigQuery V2 connection in simple connection mode and specify an update column of record data type with nested fields, you must ensure that you select
JSON
as the staging file format.
You need to specify a condition for a data driven operation. If you keep the condition field empty, the mapping fails.
You cannot use
Disable Duplicate Update Rows
target advanced property to perform a data driven operation.