Edge Release Notes - December 01, 2025

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

• New and Changed Features
• Fixes and Improvements

New and Changed Features

Destinations

• Support for Detecting Sort Keys and Distribution Keys in Amazon Redshift

  • Hevo now supports detecting sort keys and distribution keys defined on your Redshift tables during data loading. Previously, these configurations were not detected, which could cause schema evolution in the Destination to fail or behave unexpectedly.

    With this enhancement, Hevo automatically identifies the sort key and distribution key settings in the Destination tables. This improves compatibility and ensures smoother, more reliable schema evolution in Redshift Destinations.

Sources

• Support for Salesforce Formula Field Replication in Amazon Redshift

  • Added support for replicating Salesforce formula fields in Redshift Destinations. Previously, this capability was available only for Pipelines loading data into Snowflake and BigQuery.

    With this enhancement, Hevo identifies formula fields during each Pipeline run, converts them into equivalent SQL expressions, and generates corresponding views in Redshift. This ensures that calculated values stay accurate and consistently up to date across your Edge Pipelines, regardless of the Destination you use.

    Read Handling Formula Fields for more information.

Fixes and Improvements

Destinations

• Handling Column Naming Issue in Google BigQuery

  • Fixed an issue in BigQuery Destinations where column names beginning with numbers were automatically modified by Hevo by adding an underscore as a prefix, leading to a mismatch between Source and Destination column names. This issue occurred because Hevo previously sanitized such names to comply with the file format rules used during the BigQuery loading process.

    With this fix, Hevo now preserves these column names without modification, and they appear correctly in BigQuery. This fix applies to all new and existing Pipelines. For existing Pipelines, if you continue to observe a column name mismatch, resync your Pipeline.

• Handling Schema Evolution Issues in Amazon Redshift

  • Fixed an issue where Hevo could not evolve a Destination column when a previously nullable Source column was later promoted to a primary key in Pipelines using Merge load mode. This issue occurred because Redshift does not allow nullable columns to be converted to primary keys. As a result, the object was marked as Inconsistent, and replication stopped.

    With this fix, Hevo now replaces the NULL values in the Destination column with default values based on the column’s data type. This ensures that primary key changes in the Source are applied correctly in the Destination, ensuring replication continues without interruption.