• Fixed an issue that caused Pipelines to be stuck in the NoUpdate state.
• Fixed an issue where some validated Pipelines would not show preview data.
• Fixed an issue where some schedule tasks would fail to execute.
• Fixed an issue that prevented the Snowflake Snap from loading JAR files.

• Fixed an issue where the FeedMaster node would not enter maintenance mode. 
• Fixed an issue where the Load Balancer node would return an error instead of stopping further requests when in maintenance mode.

Control Plane update:

• Fixed an issue where system administrators would not receive password reset emails if email encryption was enabled. 
• Fixed an issue where users were unable to see Tasks under the Task Column of the Dashboard. 
• Fixed an issue where opening Ultra Task Details would return an Invalid ID error.
• Fixed an issue where Ultra Tasks would continuously restart.
• Fixed an issue that prevented users from updating a Snaplex with the Manage Snaplex Versions setting if the Snaplex had Slack users or channels added.
• Fixed an issue that prevented users from creating APIs in projects that had Tasks with empty Snaplex instances configured. 
• Added a read-only view for non-admin users to the Developer Portal.

• Fixed an issue where the Join Snap would fail after its input view was updated.
• Fixed an issue where the default value of newly-added properties would not appear in existing instances of the Snaplex.
• Fixed an issue where the Router Snap returned an error if a view was renamed multiple times.
• Fixed an issue where some Pipeline Execute Snaps were missing the Reuse executions to process documents checkbox.
• Fixed an issue that prevented the conditional fields of the Team Operations Snap and SQS Account from rendering.

Fixed an issue with the REST Post Snap, where the Snap delayed the fetching of documents, when the batch size is greater than or equal to one.

Fixed an issue in the SQL Server Bulk Load snap where boolean data type failed to load into BIT field.

Fixed memory leak issue when using the HDFS protocol in Hadoop and Binary Snaps.

07 Oct 2021

Enhanced the REST Post Snap to display all cookies (securedauth cookies and httponly cookies) from the CookieStore along with headers when you select the Show all headers checkbox.

Enhanced the RabbitMQ Account with a new checkbox Cluster Support that enables multiple cluster node support for RabbitMQ Consumer and RabbitMQ Producer Snaps. You can select this checkbox to enable high availability of clusters by adding multiple hosts (Host name and Port) for each cluster node.

Fixed the following issues with the Email Archive Snap where the Snap:

• Failed with an error User is authenticated but not connected, as the Snap did not re-authenticate with the server after the connection expired due to the long durations in the execution of Ultra Pipelines. 
• Caused multiple copies of the same source message in the target folder when the Snap was executed multiple times in preview.

• Fixed an issue with the Decompress Snap, where the Snap prematurely uncompressed multi-stream BZIP2 files.
• Enhanced the PGP Encrypt Snap with improved memory usage and also fixed an issue with this Snap, where the Snap failed to encrypt large size files due to the lack of memory.

• Fixed an issue with ELT Transform Snap where it may display incorrect schema only in the previews (during Pipeline validation). This occurs especially when the incoming SQL statement (defined in the SQL Statement Editor of the upstream Snap) contains one or more of the WHERE, GROUP BY, HAVING , ORDER BY, LIMIT, LIMIT followed by OFFSET, and SAMPLE clauses. Here are a few Pipeline scenarios where this issue might surface:

  • … > ELT Select (with one or more of these clauses used in the SQL Statement Editor) > ELT Transform > …

  • … > ELT Select (with or without using the SQL Statement Editor) > ELT Filter > ELT Transform > …

• Fixed an issue where the ELT Load Snap connecting to a Databricks Lakehouse Platform (DLP) instance failed to perform the load operation. Ensure that you provide a valid DBFS Folder path in the Snap's account settings as the Snap requires this folder path.

• Enhanced the ELT Database Account to support token-based authentication (Source Location Session Credentials) to S3 locations for Snowflake and Redshift target databases.
• Enhanced the ELT Aggregate Snap with the following changes:
  • Revised the field labels from:
    • GROUP BY Fields List field set > Output Field to GROUP BY Field.
    • ORDER-By Fields to ORDER-BY Fields (Aggregate Concatenation Functions Only).
  • Removed the Suggestion option for Field Name field under General Aggregate Functions List field.
  • Made the Alias Name fields in the Aggregate Concatenation Functions List and the Percentile Distribution Functions List field sets mandatory.
• If your target database is a Databricks Lakehouse Platform (DLP) instance, then the ELT Load Snap supports loading data from source CSV files that contain only comma as the separator between values.

• Fixed the following Known Issues recorded in the 4.26 GA version:
  • For a Snowflake target instance, the ELT Insert Select Snap does not suggest column names to select for the Insert Column field in the Insert Expression List.
  • The Snaps—ELT Merge Into, ELT Select, ELT Join, and ELT Filter—do not prevent the risk of SQL injection when your target database is Databricks Lakehouse Platform (DLP).

  • Intermittent null-pointer exceptions in the ELT Load Snap on Databricks Lakehouse Platform (DLP).

  • The ELT Insert Select Snap attempts to create the target table even when it exists in the Snowflake database.
  • When loading data from a JSON file into a target Databricks Lakehouse Platform (DLP) instance using an ELT Load Snap, if you choose the Drop and Create Table option as the Load Action and specify an additional column (that is not available in the JSON file) for the new table, it results in one more column null added to the new target table.
  • When you use the SQL editor in the ELT Select Snap configuration to define your SQL query, the Pipeline validation fails due to a syntax error in the following scenarios. However, the Pipeline execution works as expected. The only workaround is to drop the LIMIT clause and the optional OFFSET clause from the SQL query during Pipeline validation.

    • The query contains a LIMIT clause on a Snowflake, Redshift or Databricks Lakehouse Platform target instance: The SQL query created during Pipeline validation includes an additional LIMIT clause, for example: SELECT * FROM "STORE_DATA"."ORDERS" LIMIT 10 LIMIT 990. 

    • The query contains an OFFSET clause (supported in case of Snowflake and Redshift): The SQL query created during Pipeline validation looks like SELECT * FROM "STORE_DATA"."ORDERS" LIMIT 10 OFFSET 4 LIMIT 990.