Release Version 2.35.1

In this release, we have addressed the following issues to improve the usage and functionality of our product features. The content on this site may have changed or moved since you last viewed it. As a result, some of your bookmarks may become obsolete. Therefore, we recommend accessing the latest content via the Hevo Docs website.

In this Release

• Fixes and Improvements

Fixes and Improvements

Sources

• Handling Data Mismatch Issue in Amazon S3

  • Fixed an issue where bytes data from the Source was stored in an unreadable format in the Destination due to improper data parsing. This issue occurred because Hevo parsed bytes data from the Source and stored it directly as a string in the Destination, causing a data mismatch. With this fix, Hevo now converts the bytes data to its hexadecimal representation before storing it as a string in the Destination, ensuring that data is stored in a readable format.

    Contact Hevo Support to enable the fix for your new and existing Pipelines. For existing Pipelines, if you observe a data mismatch in your Destination tables, restart the historical load for that Source object.

User Experience

• Displaying Cluster Keys for Snowflake Destination Tables

  • Fixed an issue in the Hevo user interface (UI) that caused the cluster key icon to be missing in the Schema Mapper and the Destination Workbench for columns that are part of the cluster key in Snowflake tables.

    With this fix, the icon now appears correctly in the Hevo UI, making it easier for you to identify the columns that form the cluster key in your Destination tables.

    

    The fix will be deployed to teams across all regions in a phased manner and does not require any action from you. However, to make this fix available for your team immediately, you may contact Hevo Support.