Vertica rebranding
Vertica is being rebranded to OpenText Analytics Database starting with the 24.4 release.
Support for Debian 12.5
Vertica is now supported on Debian 12.5. This also includes support for Debian on ARM architecture.
Support for Voltage SecureData 7.0.1 and 7.0.2
Vertica is now supported with Voltage SecureData 7.0.1 and 7.0.2.
Support for additional instance types on AWS
Vertica is now supported to use i4i.12xlarge, i4i.16xlarge, and i4i.24xlarge instance types for AWS. For more details, see Supported AWS instance types.
Health Watchdog
A Health Watchdog has been implemented that automatically detects and blocks queries during bad health conditions on ther server. For more details, see Health Watchdog.
Online Upgrade
The current online upgrade policy has been renamed to ReadOnlyOnline, and we now have a new approach for online upgrades. This updated mechanism ensures the database remains active and capable of continuous writes through replication. Additionally, we implemented session transfer to further improve the upgrade experience. For more information about the upgrade policies, see Upgrading Vertica on Kubernetes.
Sandboxing on Kubernetes
Sandboxing in Kubernetes lets you quickly set up separate testing environments without the need to create a new database or reload data. This makes it easier to test Vertica features in new versions. You can stay connected to the main cluster while the upgrade is done in the sandbox. Once the upgrade is finished, you can easily bring the sandbox back into the main cluster. For more information about sandboxing, see Sandboxing on K8s.
Save restore points from Kubernetes
Previously, you could save a restore point using vsql in Vertica, but now there's an alternate method using the VerticaDB operator in Kubernetes, which is more aligned with Kubernetes environments. For more details on creating an archive and saving a restore point, see VerticaRestorePointsQuery custom resource definition.
Change owner of global temp tables
When a user account that owns tables gets deleted, the table ownership is transferred to the global account. Previously, you were unable to change the ownership of these tables from the global account. You can now change the ownership on these global temp tables.