Release Version 2.27.1

In this release, we have addressed the following issues to improve the usage and functionality of our product features. To know the list of features and integrations we are working on next, read our Upcoming Features page!

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

Destinations

• Handling Data Loading Issues for Databricks Destinations

  • Fixed an issue where Hevo was unable to load data into a Databricks table whose schema had changed. This issue occurred when the schema refresh and the sink file uploader tasks ran simultaneously. As a result, the sink file contained data structured according to the earlier schema, and Hevo was unable to load data to the Destination table. Now, if the sink file uploader task fails due to a schema mismatch, Hevo sidelines all the Events in the sink file and recreates the sink file with the updated schema.

    The fix is currently implemented for teams only in the AU (Australia) region to monitor its impact. Based on the results, it will be deployed to teams across all regions in a phased manner and does not require any action from you.

Pipelines

• Handling of Bulk Restart of Objects

  • Fixed an issue where bulk restart was not completed for all objects when more than 1000 objects were selected. The limit has now been removed, ensuring that the bulk restart is completed for all selected objects.

Sources

• Handling of Deleted Fields in Salesforce Bulk API V2 Source

  • Fixed an issue in the Salesforce Bulk API V2 integration where the deletion of a field from an object during an ongoing polling job caused the job to fail with an invalid field permission error. The invalid job ID was not cleared from the offset, causing the system to repeatedly query the deleted field and resulting in data ingestion failures. With this fix, the invalid job ID is cleared from the offset, and a new job with a new ID is initiated for seamless data ingestion.

• Improved Offset Management in Salesforce Source

  • Fixed an issue in the Salesforce integration where Hevo was not resetting the job ID for Full Load objects after all records were polled. The job ID, used as the offset for Full Load objects, was not being cleared. This caused Hevo to query the same ID repeatedly until it expired, leading to data ingestion failures. After the fix, the job ID is cleared from the offset once polling is complete, ensuring accurate data ingestion.