Error occurs even though the task runs successfully.
When you parameterize a mapping task and select a Google BigQuery connection in hybrid mode or complex mode, the following error message appears even though the task runs successfully:
Internal Error: Adapter InitDataSession failed.
Workaround: Ignore the error message.
Job fails when you configure an advanced filter condition.
When you configure an advanced filter condition and run a mapping, the mapping fails with the following error:
[ERROR] The [QUERY] job failed with the following error: [Field 'TableName.FldName' not found in table 'DatasetName.TableName'.]
Workaround: Remove the table name prefix from the field name in the filter condition and run the mapping.
Job fails when you specify a custom query usng legacy SQL and the field names of a record data type and a primitive data type.
When you configure a Google BigQuery V2 connection in simple mode and enable Use Legacy SQL For Custom Query, the mapping fails if the field names of a record data type and a primitive data type are same.
Workaround: Unselect Use Legacy SQL For Custom Query and run the mapping.