This release includes changes in behavior for the following connectors.
Amazon Redshift V2 Connector
When you configure a mapping enabled for full SQL ELT optimization and define a simple filter on a column of Super data type, the mapping fails.
Previously, the mapping ran with full SQL ELT optimization. However, zero records were written to target.
Google BigQuery V2 Connector
Effective in this release, Google BigQuery V2 Connector includes the following changes in behavior:
•In an existing mapping task configured with the Stop on errors advanced session property, the value is honored. The mapping continues to run until the number of errors reaches the set threshold value, then it fails.
Previously, the mapping failed at the first occurrence of an error, regardless of the value set for the Stop on errors advanced session property.
•If you enabled -DENABLE_NULL_FLAG_FOR_UNCACHED_LOOKUP=true property in the JVM options of the Secure Agent and have an existing mapping with the following scenarios, the mapping fetches correct data in the first row of the table:
- Configured an uncached Lookup transformation to read from Google BigQuery.
- Lookup transformation input contains null data in the first row.
Previously, the mapping fetched incorrect data in the first row of the table.
•If you enabled -DENABLE_SORTED_INPUT_FOR_LKP=true property in the JVM options of the Secure Agent and have an existing mapping with the following scenarios, the mapping fails:
- Staging is not selected as the read mode.
- The Sorted Input property is selected and the Use EXPORT DATA Statement to stage property is not selected in the lookup advanced properties.
Previously, the mapping ran successfully.
•When a Google BigQuery table is imported as a single object source in Staging mode using CSV format, and the backend schema in Google BigQuery is modified by rearranging the columns, the mapping correctly writes the data to the corresponding columns in the target table.
Previously, the mapping either failed to run or corrupted the data in the target table.
Microsoft Azure Synapse SQL Connector
Effective in this release, Microsoft Azure Synapse SQL Connector includes the following change in behavior:
•When you choose a storage type in the connection properties, the mapping shows the properties relevant to that storage type in both the source and target properties, simplifying the user experience. Previously, all storage properties were displayed.
•The mapping displays the advanced runtime properties only if the configured runtime environment is up and running. If you have configured a Secure Agent group, then the mapping displays the advanced runtime properties if at least one agent in the Secure Agent group is up and running. Previously, the mapping displayed the advanced runtime properties irrespective of the runtime environment status.
•If you configure an uncached Lookup transformation to look up data from a Microsoft Azure Synapse SQL source, where the source data of the string data type contains empty values, the uncached lookup query condition uses the correct values from the lookup object. Previously, the uncached lookup query condition used incorrect values from the lookup object.
Microsoft SQL Server Connector
Effective in this release, if you use the latest DataDirect driver and use SSL encryption, the OpenSSL version 3.0 is used by default.
Previously, the default version was OpenSSL 1.1.1.
If you want to use an earlier version of OpenSSL, add the following property in the Runtime Advanced Connection Properties field:
AllowedOpenSSLVersions=<OpenSSL_version>
Oracle Connector
Effective in this release, if you use the latest DataDirect driver and use SSL encryption, the OpenSSL version 3.0 is used by default.
Previously, the default version was OpenSSL 1.1.1.
If you want to use an earlier version of OpenSSL, add the following property in the Runtime Advanced Connection Properties field:
AllowedOpenSSLVersions=<OpenSSL_version>
Snowflake Data Cloud Connector
Effective in this release, when you configure a mapping enabled for full SQL ELT optimization and specify a temporary key column that contains the Binary data type in the Update Column field for the target, the mapping runs successfully with full SQL ELT optimization.
Previously, the mapping ran without SQL ELT optimization.