5.13 Release Notes

Upgrade guides

5.13.2 Patch Notes

Release date

Cinchy version 5.13.2 was released on December 20th, 2024.

Using an AWS Access Key to connect to DynamoDB as a data sync source will now work as expected.
We fixed a bug that was causing batch syncs between a Parquet source and a Cinchy Table destination to fail.

5.13.1 Patch Notes

Release date

Cinchy version 5.13.1 was released on December 11th, 2024.

Alpine images no longer available

Cinchy components are no longer available as variants based on linux distribution.

The following components are based on Debian only:

Connections Web API
Connections Worker
IDP
Maintenance CLI
Web
Event Listener

The default image tags will now yield Debian-based images. The -debian suffix is deprecated and should no longer be used.

Kafka Schema Registry

Kafka Schema Registry is now supported in Connections when using a Kafka Topic as a Destination.

Schema Registry is an external process that runs on a server outside of your Kafka cluster. It provides a centralized repository for managing and validating schemas for topic message data, and for serialization and deserialization of the data over the network.

Producers and consumers to Kafka topics can use schemas to ensure data consistency, verification, and compatibility as schemas evolve.

For more information on how to leverage Kafka Schema Registry within Cinchy, please review the documentation here for more information.

note

Schema Registry is not supported in syncs that use a Dynamic Topic. For real-time syncs, messages will be logged to the Execution Errors table. For batch syncs, the job will fail with a 404: Schema not found exception.

Kafka Schema Registry

Stricter Validation

Listener config validation is stricter with respect to the JSON standard. Specifically, trailing commas in arrays will appear as validation errors in the margin. While it is recommended to change the JSON to match the spec, the listener configuration will continue to work as-is.

Enhancements

Improved performance in message consumption for the Cinchy Worker when Kafka is used as a message broker for real-time syncs. [1]
Implemented more detailed error logging for REST API destinations.
The maximum timeout for exporting data was increased to 4 hours.
Azure Key Vault and AWS Secret Manager:
- Cinchy environment settings can now be stored securely in both Azure Key Vault and AWS Secret Manager, allowing for flexibility in cloud provider usage.
- Secrets support has been added for the Orchestration Scheduler and Orchestration Automation Runner components of the platform.
You are now able to configure the timeout parameter for Dynamics source and destination connectors. [2]

Dynamics Timeout Connector

Bug Fixes

The £ symbol will now correctly display within number columns.
Fixed a bug that occurred when using null values with UDF Table-valued functions.
Fixed a bug where cell comments could not be copied using ctrl + c.
Fixed a bug on Date columns where toggling the "Mandatory" property on/off would incorrectly truncate the time. [3]
Fixed a bug in Connections where the Action Type dropdown value would disappear after saving the configuration and refreshing the page.
Fixed a bug in the Worker where Cinchy HTTP requests timing out after 100s would cause the application to hang.
The Listener Config will no longer show an "Error Connecting to..." message even though it is running.
Fixed a bug when using Kafka Destination Dynamic Topics where messages would fail to send if the sync did not include calculated columns.
Fixed a bug where the the /jobs API could fail on Kubernetes deployments where MTLS and internal service URLs are being used.

Change Log

[1] More efficient Kafka Message dequeue for topics with large partition number.
[2] An extension method called SetTimeout has been added to set the Timeout to HttpClient requests. Timeout has been set to HttpClient instance for Dynamics Source and Target batch processing.
[3] Apply 'YYYY-MM-DD HH:MI:SS:MS' format to Date columns.
Updated dependencies for the collaboration log.
IBM.Data.DB2.* (3.1.0.500) updated to Net.IBM.Data.DB2.* (8.0.0.300).