When you run a mapping with Streaming as the write mode, the mapping fails with the following error for the Byte, Date/Time, and Numeric data types:

Byte:
[ERROR] The following error occurred while loading data: [Failed to decode bytes input. Byte fields must be base64 encoded, value: java.nio.HeapByteBuffer[pos=0 lim=14 cap=14].]
Date/Time:
[ERROR] The following error occurred while loading data: [Epoch second value -2189418433211000 out of range]
Numeric:
[ERROR] Error Occured for Transformation - Source while writing the data to DTM Buffer - Data Conversion Failed

When the BigQuery Storage API is enabled in the connection and the source object in a mapping is a view with key-range partitioning defined, the mapping runs successfully initially. However, when you rerun the mapping, the staging tables created during the first run are not deleted and the mapping fails with the following error:

When you configure the BigQuery Storage API to stage files in the connection and run a mapping, the mapping fails in the following scenarios:

When the mapping reads data from multiple source objects.
When an connected uncached Lookup transformation is configured for view objects.
When the mapping is enabled with source
SQL ELT optimization
.

When you configure an uncached Lookup transformation in a mapping to look up data from a Google BigQuery source, and the source column contains a NULL value in the first row, data corruption occurs in the target.

When you edit the metadata of an existing mapping and a column name contains special character, the mapping fails with the following error:

When you run a mapping task that is based on a mapping in SQL ELT mode, and the mapping contains a parameterized unconnected Lookup transformation, the task fails with the following error:

When the lookup source contains a decimal data type and the precision of the value is greater than 28 in a Lookup transformation, the mapping fails with the following error: