Release Version 2.39
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.
This release note also includes the fixes provided in all the minor releases since 2.38.
To know the complete list of features available for early adoption before these are made generally available to all customers, read our Early Access page.
In this Release
New and Changed Features
Sources
-
Removed Support for Products Object in Recharge (Release 2.38.1)
-
Effective June 30, 2025, Recharge deprecated the Products object in API version 2021-01. As a result, Hevo no longer replicates data from this object. However, the same data continues to be available through the Plans object, which Hevo fetches using API version 2021-11.
This change applies to all new and existing Pipelines.
-
-
Support for Labels Object in Google Ads
-
Added support for ingesting data for the Labels object as a core object in Google Ads. Labels allow you to organize and analyze your entities, such as campaigns, ad groups, ads, or keywords, by grouping them under custom labels, making it easier to filter, report, and track performance across multiple entities. This object is available in all new and existing Pipelines created with this Source.
Read Data Model.
-
-
Support for Labels Object in Microsoft Ads
-
Added support for ingesting data for the Labels object as a core object in Microsoft Ads. The Labels object allows you to organize and analyze your Microsoft Ads entities, such as campaigns, ad groups, ads, or keywords, by grouping them under custom labels. This makes it easier to filter, report, and track performance across multiple entities. This object is available in all new and existing Pipelines created with this Source.
Read Data Model.
-
-
Support for PostgreSQL Database Version 17.x (Added in Release 2.38.2)
- Introduced support for creating Pipelines with PostgreSQL database version 17.x. This applies to Pipelines created with any variant of the PostgreSQL Source.
-
Optimized Large Transaction Handling in Oracle (Edge)
- Improved handling and expanded support for SQLite, including better management of large transactions in Oracle. The latest updates have been tested to support up to 50 million records per transaction.
-
Support for Amazon Aurora MySQL as a Source (Edge)
- Integrated Amazon Aurora MySQL as a Source for creating Pipelines. Amazon Aurora MySQL offers high performance and availability while being cost-effective and easy to manage, making it ideal for reliable data ingestion and replication.
-
Support for Azure PostgreSQL (Edge)
- Integrated Azure PostgreSQL as a Source for creating Pipelines. Azure PostgreSQL is fully managed, enterprise-ready community PostgreSQL database as a service that can handle mission-critical workloads with predictable performance, security, high availability, and dynamic scalability.
-
Support for SQL Server Change Tracking as a Source (Edge)
- Integrated SQL Server Change Tracking as a Source for creating Pipelines. SQL Server is a relational database management system known for its scalability, security, and performance, making it suitable for a wide range of enterprise applications. The Change Tracking feature in SQL Server enables efficient data replication from databases by tracking and capturing changes made to them. This reduces the number of queries required to run on the database, optimizing performance. The supported variants for this Source are SQL Server Change Tracking and Amazon RDS SQL Server Change Tracking.
-
WAL Slot Monitoring in PostgreSQL (Edge)
- Users can now modify the Write-Ahead Logging (WAL) slot monitoring threshold.
Data Ingestion
-
Run Incremental and Historical Ingestions in Parallel (Edge)
- Earlier, only one ingestion job, either incremental or historical, could run at a time, leading to potential delays in data processing. Now, both jobs can run simultaneously, with incremental data loading immediately after the completion of the historical load.
Data Loading
-
Support for Changing the Load Mode at the Object Level (Edge)
- Introduced the ability to change the load mode for objects during and post-Pipeline creation. Previously, the load mode could only be set at the Pipeline level, which was applied to all objects with no option to change it later. With this enhancement, you can now change the load mode for individual objects on the Object Configuration page, providing more flexibility and control over how your data is loaded. Read Changing the load mode for an object for more information.
Destinations
-
Edit Snowflake Key Pair Authentication (Edge)
- Hevo now supports editing your key pair authentication, making the connection more secure. Read Modifying Snowflake Destination Configuration for more information.
-
Support for Amazon Redshift as a Destination (Edge)
- Integrated Amazon Redshift as a data warehouse Destination for creating Pipelines. Amazon Redshift enables scalable data storage and high-performance analytics, making it ideal for large-scale data processing and business intelligence.
-
Unquoted Identifiers in Table and Column Names in Snowflake (Edge)
- A Pipeline configuration option to manage quoted identifiers. This will allow users to enable or disable quotes around table and column names, ensuring compatibility with their existing Snowflake DDL queries.
Pipelines
-
Managing Alert Recipients (Edge)
- Enhanced the Alerts system in Hevo Edge, allowing users with administrator and collaborator roles in Hevo to add recipients. Email addresses and or Slack channels can be added as recipients and subscribed to Pipelines to receive notifications from alerts that may require their attention.
-
Pipeline Configuration Editing (Edge)
- You can now edit the following fields in your Pipelines:
-
Schema Evolution (Edge)
- Earlier, adding a new column or object to a Pipeline triggered a drop and load operation, replacing all existing data in the Destination. Now, when a new column or object is added, it is seamlessly integrated into the Destination without dropping any existing data. The operation modifies the existing data for changes, providing an option to re-create the object and reload its historical data. The incremental data for the new column or object will be loaded during the next incremental run.
-
Upgrade: Standard to Edge (Edge)
- You can now upgrade your PostgreSQL Standard Pipelines to Snowflake. However, this upgrade currently comes with certain limitations:
Fixes and Improvements
Destinations
-
Handling Data Type Auto Promotion Issue in PostgreSQL Destination (Fixed in Release 2.38.1)
-
Fixed an issue where, in some cases, Hevo was unable to automatically promote the data type of the Destination column to store Source data of a compatible data type. This issue occurred when the Destination column name approached PostgreSQL’s 63 character limit for table and column names. During internal handling, Hevo added prefixes to the column name, which caused the final name to exceed the limit. As a result, data type promotion failed, and some Events could not be loaded to the Destination.
With this fix, Hevo now manages column naming and data type auto-promotion, and proceeds as expected. This ensures that all Events are correctly loaded to the Destination. This fix applies to all new and existing Pipelines.
-
Pipelines
-
Handling API Timeout Issue while Fetching Objects List for Facebook Ads Source (Fixed in Release 2.38.3)
-
Fixed an issue in Pipelines where the Hevo UI sometimes took longer than expected to display the list of Source objects in the Pipeline Detailed View. This occurred because fetching the object list required an additional API call to retrieve the OAuth token ID for the Pipeline, which was routed through servers in the Asia region. For Pipelines in other regions, this additional latency caused the API to exceed its 30-second time limit and time out.
With this fix, Hevo removes the unnecessary API call to the Asia server, reducing latency and ensuring the object list loads within the time limit.
This fix applies to all new and existing Pipelines.
-
Sources
-
Handling Connection Issue in Amazon RDS PostgreSQL Source (Fixed in Release 2.38.2)
-
Fixed an issue where connecting to Amazon RDS PostgreSQL failed with the error, For input string: “database_version”. This issue occurred because Hevo expected the database version to be in a simple format, for example, 11.22 to check compatibility with logical replication. However, RDS sometimes adds a suffix, such as -rds, to the version string, which caused the compatibility check to fail.
With this fix, Hevo now correctly interprets such version strings for RDS instances, ensuring a successful connection with the Source. To enable this fix for your team, contact Hevo Support.
-
-
Handling Inconsistent Data Refresher Tasks for Google Sheets (Fixed in Release 2.38.3)
-
Fixed an issue where the refresher task for Google Sheets was triggered only if exactly 24 hours had passed since the last run. This caused scenarios where the refresher task ran inconsistently if the previous refresher task ended slightly under 24 hours, creating a gap between runs and resulting in missing data.
With this fix, the refresh timing logic has been adjusted to account for minor differences in task completion time, ensuring that the refresher task runs consistently every day and eliminating gaps in data refresh. This fix applies to all new and existing Pipelines.
-
-
Handling NULL values in Enum data for PostgreSQL Source (Fixed in Release 2.38.2)
-
Fixed an issue affecting all variants of PostgreSQL Source where columns containing arrays of enum values were incorrectly displayed as NULL in the Destination table. This issue occurred because Hevo could not correctly identify enum array columns when they were defined inside a named schema and skipped them during ingestion. For example, if a column such as customer_data was defined inside a schema called store, it was internally represented as “store”.”_customer_data”. Hevo failed to recognize this as a valid array and dropped the column while processing the record, resulting in NULL values in the Destination.
With this fix, Hevo now correctly handles such types of columns, ensuring that the data is retrieved and ingested accurately. To enable the fix for your existing and new Pipelines, contact Hevo Support. If you observe NULL values in your Destination tables, you must enable the fix and then restart the historical load for the object.
-
-
Handling Unsupported Object Issue in Salesforce and Salesforce Bulk API V2 (Fixed in Release 2.38.3)
- Fixed an issue where the unsupported Salesforce object ActivityMetric was visible in the UI and could be selected for ingestion. This issue occurred because Hevo did not validate whether the object was supported and queryable before adding it to the Pipeline schema. With this fix, ActivityMetric has been removed from the schema and is no longer selectable, preventing ingestion failures.
Documentation Updates
The following pages have been created, enhanced, or removed in Release 2.39:
Account Management
Data Ingestion
Data Loading
Destinations
-
Destination FAQs
Getting Started
Pipelines
Sources
-
Database Source FAQs
-
Google Ads
- Creating a Custom Report (New)
-
PostgreSQL FAQs
-
SQL Server FAQs
Transform
-
dbt Models
-
SQL Models