Features

• Added 'named' throttle and concurrency support, allowing per-user throttling and active query limits.
• Added support for regular expression matching on API invalidations (via HTTP API).
• Added support for regular expression matching for most metadata rules.
• Initial beta support for row deletion capabilities and data masking.
• Added Greenplum proxy (behaves as Postgres proxy for now).

Fixes

• Resolved issue that could prevent a proxy from logging to the manager.

Features

• Improved let’s encrypt interface to allow aliases and selection of the alias in the vdb, along with documentation.
• Now handles special case of @@rowcount for Microsoft Entity Framework requests and Microsoft SQL Server.

Fixes

• Resolved ODBC TLS compatibility issue for SQL Server involving TLS frame lengths.

Features

• Added Amazon Redshift as new proxy type.
• Added Amazon Redshift driver in new baseline configuration.
• Adjusted how Cloudwatch metrics are generated, putting them in the “Heimdall-proxy” category, and making them multi-dimensional metrics, allowing for easier generation of dashboards on autoscaling groups.
• Added support for auto-detection of Postgres sequence handling that can impact caching, disabling caching and read/write split when used in a query.
• Updated AWS SDK version.
• Improved ${host} handling for SaaS deployments, allowing SQL authentication to drive what cluster a given user should be served from dynamically.
• Adjusted default PostgreSQL sslmode to prefer.
• Documentation updates.

Fixes

• Resolved issue with Global AWS Aurora clusters, where remote clusters would use the wrong region name.
• Fixed an issue that can cause issues with SQL Server while caching is enabled.
• Resolved issue where connection pooling was not activated if LB was not also active.
• Resolved issue of MySQL driver not loading cleanly on proxy startup due to timing issues in some cases.

Features

• Improved auto-nocache and no-read/write split for Postgres sequences, improving Odoo compatibility.

Fixes

• Updated the Postgres driver to include a fix that prevented back-end TLS connections from working with the custom PG driver – This driver will need to be updated manually.
• Resolve issue that at times prevented proxy initialization when the built-in port 80 health check was active.
• Resolved issue with ${schema} replacement variable of the variable was set, but empty.

Features

• Improved handling of all proxies with large result-sets to avoid memory overflows.
• Added a distinct download button on the software management tab to download the current software, simplifying rollbacks.
• Added Graviton3 instances to AWS Marketplace offering (pending).

Fixes

• Resolved issue where cloudwatch logging could cause heartbeat delays.

Features

• Added an internal Postgres driver that supports streaming of arbitrary large result-sets. (Note: This driver should not be used with other applications as it is not 100% API complete for the JDBC API. An upgrade to this version of code will not update the driver however, this step needs to be done manually.)
• If the TLS certificates used by Heimdall have less than 7 days until expiration, each day an alert will now be generated on the UI.
• Added a custom cache key option to use the schema as part of the key creation.
• Added a “lite” debug option to trigger dumping one second of verbose debug logs in the event of an exception, to reduce the size when debugging rare issues.
• Added “since started” counters to the JMX interface.

Fixes

• Resolved several code path issues with “set search_path to <path>” where the schema was not handled properly.
• Resolved an issue where if the internal health-check was enabled, but the interval was set to 0, the proxy would never start listening.

Features

• Added a default value of ‘0’ for the MySQL JDBC driver parameter of “netTimeoutForStreamingResults”.
• Small build and test changes.