4.24

Patch

• Enhances the Teradata Execute Snap by adding a new field, Advanced options, which extends support with microsecond precision for TIMESTAMP data type.
• Fixes an issue in the TPT Load Snap where the Snap failed to load data into the table while creating an output.

• Fixes an issue with the TPT LoadSnap wherein now a null value is loaded as null and empty string is loaded as empty string.

• • This fix may cause existing pipelines to fail if empty string values are expected to be loaded as null.

  • Following are the new configurations:

    • VARCHAR QuotedData= Optional

    • VARCHAR OpenQuoteMark= \”

    • VARCHAR NullColumns= Yes

Enhances the Teradata Select Snap to return only the selected output fields or columns in the output schema (second output view) using the Fetch Output Fields In Schema check box. If the Output Fields field is empty all the columns are visible.

• Fixes an issue with TPT Load Snap wherein now a null value is load as null and empty string is load as empty string.

4.21

Patch

Fixes the issue where Snowflake SCD2 Snap generates two output documents despite no changes to Cause-historization fields with DATE, TIME and TIMESTAMP Snowflake data types, and with Ignore unchanged rows field selected.

4.21 Patch

Fixes the following issues with DB Snaps:

• The connection thread waits indefinitely causing the subsequent connection requests to become unresponsive.
• Connection leaks occur during Pipeline execution.

4.21 Patch

Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends. 

4.19 Patch 

• An expression is used in the Update condition property.
• Input data contain the character '?'.

Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.

• Fixed an issue with the Teradata Execute Snap wherein the Snap would send the input document to the output view even if the Pass through field is not selected in the Snap configuration. With this fix, the Snap sends the input document to the output view, under the key original, only if you select the Pass through field.
• Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.

4.15 Patch 

Replaced Max idle time and Idle connection test period properties with Max life time and Idle Timeout properties respectively, in the Account configuration. The new properties fix the connection release issues that were occurring due to default/restricted DB Account settings.

snapsmrc486

snapsmrc480

snapsmrc414

Added Auto commit property to the Select and Execute Snaps at the Snap level to support overriding of the Auto commit property at the Account level.

4.9.0 Patch

Fixed an issue regarding connection not closed after login failure; Expose autocommit for "Select into" statement in PostgreSQL Execute Snap and Redshift Execute Snap

• Enhanced the Output view of the Snap with Order Summary field that displays the output values (added to the out, err, status, classpath and env fields of the single output view that display the subprocess only).

• Teradata Export to HDFS Snap supported with Dynamic account.

snapsmrc398

• Introduced the TPT Delete, Insert, Load, Upsert and Update Snaps in this release.
• Introduced Teradata Export to HDFS Snap in this release.
• Info tab added to accounts.
• Database accounts now invalidate connection pools if account properties are modified and login attempts fail.

snapsmrc382

• Introduced the Teradata FastLoad and Execute Snaps in this release.
• Migration impact: In Teradata FastExport, the values of the Data Format field have been standardized to be in all caps. Existing pipelines that use the values of Binary, Text, or Unformatted will fail unless the new value of BINARY, TEXT, or UNFORMAT are used.

Snap Pack introduced in 4.6.0. This includes only Teradata extract functionality to move data out of Teradata database using the FastExport Utility. It does not include Snaps for load, select, insert, delete, execute or others at this time. It also does not utilize the Teradata Parallel Transporter to extract data.