Release Version 2.38.2

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

Sources

• Support for PostgreSQL Database Version 17.x

  • Introduced support for creating Pipelines with PostgreSQL database version 17.x. This applies to Pipelines created with any variant of the PostgreSQL Source.

Fixes and Improvements

Sources

• Handling Connection Issue in Amazon RDS PostgreSQL Source

  • 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 NULL values in Enum data for PostgreSQL Source

  • 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.