New and changed in Vertica 25.1

New features and changes in Vertica 25.1.

Client proxy for subclusters in Kubernetes

Connections are now redirected through the client proxy before reaching the Vertica nodes. For details on enabling client proxy, creating replicas, and connecting to Vertica nodes through the proxy, see Client proxy for subclusters.

Shut down sandbox and subcluster in Kubernetes

You can now stop and shut down the sandbox along with all its subclusters. For more information, see Sandboxing on K8s. You can also stop and shut down individual subclusters in the main cluster. See Scaling subclusters.

Async replication in Kubernetes

Previously, Kubernetes supported only synchronous replication which required replicating the entire database. Now, replication is asynchronous by default. The VerticaDB operator initiates replication and checks progress periodically without waiting for the replication to complete. Additionally, partial replication is supported, allowing you to replicate specific schemas or tables based on names or wildcard patterns to be replicated instead of the entire database. This provides better control and efficiency in replication tasks. For more information, see VerticaReplicator custom resource definition.

Execute data loader file parameters

You can now specify parameters such as compression and node assignment for each file in the WITH FILES clause of EXECUTE DATA LOADER. For more details about parameter transfer and override rules, see EXECUTE DATA LOADER.

Health Watchdog tuning knobs

Tuning knobs have been added to the Health Watchdog to tune it to your system. For more details, see Health Watchdog.