Forum Discussion

dmiller's avatar
dmiller
Former Employee
8 years ago

SnapLogic May 2018 Release, UAT Notification

We are pleased to announce the May 2018 release (4.13) of the SnapLogic Enterprise Integration Cloud. The first update to UAT will take place on April 20, 2018 at 11:00 AM PT / 7:00 PM GMT. The relea...
dmiller's avatar
dmiller
Former Employee
8 years ago

The first UAT update of SnapLogic Enterprise Integration Cloud Spring 2018 was completed on 27/April/18. The following items were updated since the initial UAT push.

Platform Updates

  • Fixed an issue where a child pipeline execution on the current node looks for dependencies in the parent pipeline’s project instead of the child pipeline’s project.
  • Fixed an issue with task update API that causes the task to enable after an update.
  • Added details to the pipeline failure notification email.
  • Fixed an error condition handling when creating API proxy in Apigee.
  • Fixed an issue when passing encrypted properties using the Metadata Snaps.
  • Fixed an issue that causes CSV formatting to fail with unicode delimiter character.

Snap Updates

  • Adobe Cloud Platform: Dataset suggestion now displays all datasets and not just the first 20.
  • Box: Fixed an issue wherein the Box Read Snap enters an infinite loop situation for connection errors.
  • Confluent Kafka: Fixed an issue with the Confluent Kafka Consumer Snap that did not respect the acknowledgement timeout window on a per message basis.
  • Hadoop: Fixed an issue with the HDFS and Parquet Snaps that presume a default port value of 8020, preventing directory and file suggestions for nameservice-enabled nodes.
  • JDBC: Updated the Hikari connection pool management library version. This has resulted in a breaking change for JDBC3 drivers. The newer version requires databases to be able to support a validation query of “SELECT 1;” or have the driver itself implement a custom validation method. Some older JDBC3 drivers may not have such an implementation, meaning those drivers configured in a JDBC Account may no longer validate if the “Database name” setting has the value of “Auto-detect.” For example, DB2-based JDBC Accounts must explicitly choose “DB2” from the “Database name” setting. JDBC4 drivers are not affected by this change.
  • Oracle: Fixed a regression in the Oracle Bulk Load Snap due to null values resulting in records being rejected.
  • RabbitMQ: Fixed an issue with the RabbitMQ Consumer Snap that did not output the “deliveryTag” and “redelivered” fields for use when re-consuming an unacknowledged/rejected message.

UI Update

  • Fixed an issue wherein pipelines did not print.

Release schedule is planned as follows:

Date POD DownTime Details Status
Friday, April 20 11 AM PDT UAT 4 hours Release to UAT: Status Complete COMPLETED
Tuesday, April 24 9 AM PDT UAT 4 hours 4.13 Feature Webinar on UAT COMPLETED
Friday, April 27 11 AM PDT UAT 4 hours UAT Update #1 COMPLETED
Friday, May 4 11 AM PDT UAT 4 hours UAT Update #2 PENDING
Saturday, May 12 9 PM PDT ELASTIC 2 hours 4.13 Release to Production (2-hr Planned Downtime) PENDING
Thursday, May 179 AM PDT ELASTIC 4.13 Production Feature Webinar PENDING
Saturday, June 9 9pm PDT ELASTIC Update of remaining Snaplexes to 4.13 PENDING

​How do I learn more?

If you are unable to attend the webinar on April 24th or May 17th, visit the documentation site with the UAT UPDATE#1 deployment to UAT for additional details on new and enhanced platform features and Snap Packs.

Be sure to join in the conversation in the SnapLogic Community.

Lastly, contact us directly if you have questions about the release at support@snaplogic.com.