New fields are available when working with captured and ignored exceptions
Prior to this update, it was possible to ignore all or specific exceptions during flow execution. All ignored exceptions were captured and stored in the etlConfig object and could be used later to save the error in a database or send a notification.
In this update, we added new fields to the exception object. The following example shows how to use new fields when sending notifications about ignored exceptions.
Automatic conversion of the SQL Server TIMESTAMP field to LONG
Prior to this update, the MS SQL Server binary TIMESTAMP and ROWVERSION fields were loaded as a byte array and mapped to the BINARY data type. Note that the BINARY fields are automatically Base46 encoded when saved as a part of the CSV file, which was causing an issue when loading tables with these fields into the Snowflake or Amazon Redshift.
In this update, we introduced an automatic conversion of the MS SQL Server binary TIMESTAMP and ROWVERSION fields to LONG when creating CSV files. It is no longer required to use SQL to translate the TIMESTAMP or ROWVERSION to the number.