Changed behavior

Effective in this release, mappings in SQL ELT mode fail if a source field of string data type contains data that is not valid and is mapped to a target field of numeric data type.

Previously, these mappings did not fail, and instead, null values were written to the target field where the source field contained data that is not valid.

Effective in this release, a mapping fetches the list of tables from the Greenplum database regardless of the case of the database name.

Previously, if the database name from where you retrieve data was in uppercase, the mapping would return an empty list of tables.

Effective in this release, when you map a date or datetime field in the source to a string data type in the target, the mapping writes data to the target in the MM/dd/yyyy HH:mm:ss format, a 24-hour format.

Previously, the data was written to the target in the MM/dd/yyyy hh:mm:ss format, a 12-hour format, resulting in data mismatch with the source.

Effective in this release, the MongoDB V2 mapping writes Null values as Null to the target.

Previously, the mapping wrote Null values as 0 to the target. This change in behavior doesn't apply to mappings in advanced mode.

Effective in this release, when you run a Snowflake Data Cloud mapping, the session log does not capture the Snowflake-triggered warning messages, it only captures relevant information about your mapping.

Previously, the Snowflake-triggered warning messages were also captured in the session log.