New features

This guide briefly describes the new features introduced in the most recent releases of Vertica and provides references to detailed information in the documentation set.

1: List of new features
2: OpenText Core Analytics Database
3: Deprecated and removed functionality
4: Eon Mode
5: New and changed in Vertica 24.4

5.1: Health Watchdog
5.2: Upgrading Vertica on Kubernetes
5.3: Sandboxing on Kubernetes
5.4: Save restore points from Kubernetes

This guide briefly describes the new features introduced in the most recent releases of Vertica and provides references to detailed information in the documentation set.

For known and fixed issues in the most recent release, see the Vertica Release Notes.

1 - List of new features

2 - OpenText Core Analytics Database

OTCAD provides data analysts and business intelligence professionals with access to powerful analytics and reporting tools, facilitating efficient insights from large datasets.

About OpenText Core Analytics Database (OTCAD)

OpenText Core Analytics Database (OTCAD) provides a managed database service for your data management needs, as it integrates with leading cloud service providers such as AWS. OTCAD:

Manages your data and helps you avoid daily maintenance of a data warehouse or data lake environment.
Provides data analysts and business intelligence professionals with access to powerful analytics and reporting tools, facilitating efficient insights from large datasets.
Uses Vertica running on Kubernetes as the main engine for the data warehouse or data lake.

OTCAD is a cloud solution that enhances the speed and scalability of a Vertica analytics database without the need to manage hardware. Use OTCAD to build databases securely and scale them to large amounts of data in the cloud.

OTCAD supports machine learning with VerticaPy for data science and AI-driven data science applications. It also supports the following third-party applications:

IBM Cognos BI
Grafana
Informatica PowerCenter
DbVisualizer
DBeaver
Domino Data Lab

To get access to OTCAD, contact your sales representative or contact us.

3 - Deprecated and removed functionality

Vertica retires functionality in two phases:.

Vertica retires functionality in two phases:

Deprecated: Vertica announces deprecated features and functionality in a major or minor release. Deprecated features remain in the product and are functional. Published release documentation announces deprecation on this page. When users access this functionality, it may return informational messages about its pending removal.
Removed: Vertica removes a feature in a major or minor release that follows the deprecation announcement. Users can no longer access the functionality, and this page is updated to verify removal (see History, below). Documentation that describes this functionality is removed, but remains in previous documentation versions.

Deprecated

Removed

History

The following functionality or support has been deprecated or removed as indicated:

Functionality	Component	Deprecated in:	Removed in:
`OAuth2JITClient` security parameter.	Server	24.2.0
The following Helm chart parameters: `logging.maxFileSize` `logging.maxFileAge` `logging.filePath` `logging.maxFileRotation`	Kubernetes	24.2.0
The following JDBC and ODBC connection properties: OAuthRefreshToken/oauthrefreshtoken OAuthClientSecret/oauthclientsecret oauthtruststorepath (JDBC only) oauthtruststorepassword (JDBC only)	Client drivers	24.1.0
Integration with the Linux `logrotate` utility	Server	24.1.0
vbr utility in Kubernetes pods	Kubernetes		24.1.0
Scrutinize in Kubernetes pods	Kubernetes		24.1.0
`v1beta1` VerticaDB custom resource definition API version	Kubernetes	23.4.0
`serviceAccountNameOverride` Helm chart parameter	Kubernetes	23.4.0	24.1.0
`skipRoleAndRoleBindingCreation` Helm chart parameter	Kubernetes	23.4.0	24.1.0
`spec.communal.kerberosRealm` VerticaDB custom resource definition parameter	Kubernetes	23.4.0	24.1.0
`spec.communal.kerberosServiceName` VerticaDB custom resource definition parameter	Kubernetes	23.4.0	24.1.0
`spec.temporarySubclusterRouting` VerticaDB custom resource definition parameter	Kubernetes	23.4.0	24.1.0
Vertica Kubernetes (No keys) image	Kubernetes	23.4.0	24.1.0
Vertica Kubernetes admintools support	Kubernetes	23.4.0	24.1.0
Oracle Enterprise Linux 6.x (Red Hat compatible kernels only)	Supported platforms	23.4.0	24.1.0
Oracle Enterprise Linux 7.x (Red Hat compatible kernels only)	Supported platforms	23.4.0
Red Hat Enterprise Linux 7.x (RHEL 7) support	Supported platforms	23.4.0	24.1.0
The following log search tokenizers: `v_txtindex.AdvancedLogTokenizer` `v_txtindex.BasicLogTokenizer` `v_txtindex.WhitespaceLogTokenizer` `logWordITokenizerPositionFactory` and `logWordITokenizerFactory` from the `v_txtindex.logSearchLib` library	Server	23.4.0	24.1.0
DHParams	Server	23.3.0
OAuthJsonConfig and oauthjsonconfig	Client drivers	23.3.0
Visual Studio 2012, 2013, and 2015 plug-ins and the Microsoft Connectivity Pack	Client drivers	12.0.4	23.3.0
ADO.NET driver support for .NET 3.5	Client drivers	12.0.3
`prometheus.createServiceMonitor` Helm chart parameter	Kubernetes	12.0.3
`webhook.caBundle` Helm chart parameter	Kubernetes	12.0.3	24.1.0
cert-manager for Helm chart TLS configuration	Kubernetes	12.0.2	23.3.0
Use `webhook.certSource` parameter to generate certificates internally or provide custom certificates. See Helm chart parameters.	Kubernetes	12.0.2
The following Kafka user-defined session parameters: kafka_SSL_CA kafka_SSL_Certificate kafka_SSL_PrivateKey_Secret kafka_SSL_PrivateKeyPassword_secret kafka_Enable_SSL	Kafka	12.0.3
vsql support for macOS 10.12-10.14	Client drivers		12.0.3
CA bundles	Security	12.0.2
The following parameters for CREATE NOTIFIER and ALTER NOTIFIER: TLSMODE CA BUNDLE CERTIFICATE	Security	12.0.2
The TLSMODE PREFER parameter for CONNECT TO VERTICA.	Security	12.0.2
JDBC 4.0 and 4.1 support	Client drivers	12.0.2	23.4.0
Support for Visual Studio 2008 and 2010 plug-ins	Client drivers	12.0.2	12.0.3
Internet Explorer 11 support	Management Console		12.0.1
ODBC support for macOS 10.12-10.14	Client drivers		12.0
The following ODBC/JDBC OAuth parameters: OAuthAccessToken/oauthaccesstoken OAuthRefreshToken/oauthrefreshtoken OAuthClientId/oauthclientid OAuthClientSecret/oauthclientsecret OAuthTokenUrl/oauthtokenurl OAuthDiscoveryUrl/oauthdiscoveryurl OAuthScope/oauthscope	Client drivers	12.0
`hive_partition_cols` parameter for PARQUET and ORC parsers	Server	12.0
The following ODBC/JDBC OAuth parameters: OAuthAccessToken/oauthaccesstoken OAuthRefreshToken/oauthrefreshtoken OAuthClientId/oauthclientid OAuthClientSecret/oauthclientsecret OAuthTokenUrl/oauthtokenurl OAuthDiscoveryUrl/oauthdiscoveryurl OAuthScope/oauthscope	Client drivers	12.0
INFER_EXTERNAL_TABLE_DDL function	Server	11.1.1
Admission Controller Webhook image	Kubernetes	11.0.1	11.0.2
Admission Controller Helm chart	Kubernetes	11.0.1
Shared DATA and DATA,TEMP storage locations	Server	11.0.1
DESIGN_ALL option for EXPORT_CATALOG()	Server	11.0
HDFSUseWebHDFS configuration parameter and LibHDFS++	Server	11.0
INFER_EXTERNAL_TABLE_DDL (path, table) syntax	Server	11.0	11.1.1
AWS library functions: AWS_GET_CONFIG AWS_SET_CONFIG S3EXPORT S3EXPORT_PARTITION	Server	11.0	12.0
Vertica Spark connector V1	Client	11.0
admintools `db_add_subcluster` `--is-secondary` argument	Server	11.0
Red Hat Enterprise Linux/CentOS 6.x	Server	10.1.1	11.0
STRING_TO_ARRAY(array,delimiter) syntax	Server	10.1.1
Vertica JDBC API com.vertica.jdbc.kv package	Client Drivers	10.1
ARRAY_CONTAINS function	Server	10.1
Client-server TLS parameters: SSLCertificate SSLPrivateKey SSLCA EnableSSL LDAP authentication parameters: tls_key tls_cert tls_cacert tls_reqcert LDAPLink and LDAPLink dry-run parameters: LDAPLinkTLSCACert LDAPLinkTLSCADir LDAPLinkStartTLS LDAPLinkTLSReqCert	Server	10.1	11.0
MD5 hashing algorithm for user passwords	Server	10.1
Reading structs from ORC files as expanded columns	Server	10.1	11.0
vbr configuration section [S3] and S3 configuration parameters	Server	10.1
flatten_complex_type_nulls parameter to the ORC and Parquet parsers	Server	10.1	11.0
System table WOS_CONTAINER_STORAGE	Server	10.0.1	11.0.2
skip_strong_schema_match parameter to the Parquet parser	Server	10.0.1	10.1
Specifying segmentation on specific nodes	Server	10.0.1
DBD meta-function DESIGNER_SET_ANALYZE_CORRELATIONS_MODE	Server	10.0.1	11.0.1
Meta-function ANALYZE_CORRELATIONS	Server	10.0
Eon Mode meta-function BACKGROUND_DEPOT_WARMING	Server	10.0
Reading structs from Parquet files as expanded columns	Server	10.0	10.1
Eon Mode meta-functions: SET_DEPOT_PIN_POLICY CLEAR_DEPOT_PIN_POLICY	Server	10.0	10.1
vbr configuration parameter SnapshotEpochLagFailureThreshold	Server	10.0
Array-specific functions: array_min array_max array_sum array_avg	Server	10.0	10.1
DMLTargetDirect configuration parameter	Server	10.0
HiveMetadataCacheSizeMB configuration parameter	Server	10.0	10.1
MoveOutInterval	Server	10.0
MoveOutMaxAgeTime	Server	10.0
MoveOutSizePct	Server	10.0
Windows 7	Client Drivers		9.3.1
DATABASE_PARAMETERS admintools command	Server	9.3.1
Write-optimized store (WOS)	Server	9.3	10.0
`7.2_upgrade` vbr task	Server	9.3
DropFailedToActivateSubscriptions configuration parameter	Server	9.3	10.0
`--skip-fs-checks`	Server	9.2.1
32-bit ODBC Linux and OS X client drivers	Client	9.2.1	9.3
Vertica Python client	Client	9.2.1	10.0
macOS 10.11	Client	9.2.1
DisableDirectToCommunalStorageWrites configuration parameter	Server	9.2.1
CONNECT_TO_VERTICA meta-function	Server	9.2.1	9.3
ReuseDataConnections configuration parameter	Server	9.2.1	9.3
Network interfaces (superseded by network addresses)	Server	9.2
Database branching	Server	9.2	10.0
KERBEROS_HDFS_CONFIG_CHECK meta-function	Server	9.2
Java 5 support	JDBC Client	9.2	9.2.1
Configuration parameters for enabling projections with aggregated data: EnableExprsInProjections EnableGroupByProjections EnableTopKProjections EnableUDTProjections	Server	9.2
DISABLE_ELASTIC_CLUSTER()	Server	9.1.1	11.0
`eof_timeout` parameter of KafkaSource	Server	9.1.1	9.2
Windows Server 2012	Server	9.1.1
Debian 7.6, 7.7	Client driver	9.1.1	9.2.1
IdolLib function library	Server	9.1	9.1.1
SSL certificates that contain weak CA signatures such as MD5	Server	9.1
HCatalogConnectorUseLibHDFSPP configuration parameter	Server	9.1
S3 UDSource	Server	9.1	9.1.1
HCatalog Connector support for WebHCat	Server	9.1
`partition_key` column in system tables STRATA and STRATA_STRUCTURES	Server	9.1	10.0.1
Vertica Pulse	Server	9.0.1	9.1.1
Support for SQL Server 2008	Server	9.0.1	9.0.1
SUMMARIZE_MODEL meta-function	Server	9.0	9.1
`RestrictSystemTable` parameter	Server	9.0.1
S3EXPORT `multipart` parameter	Server	9.0
EnableStorageBundling configuration parameter	Server	9.0
Machine Learning for Predictive Analytics package parameter `key_columns` for data preparation functions.	Server	9.0	9.0.1
DROP_PARTITION meta-function, superseded by DROP_PARTITIONS	Server	9.0
Machine Learning for Predictive Analytics package parameter `owner`.	Server	8.1.1	9.0
Backup and restore `--setupconfig` command	Server	8.1	9.1.1
SET_RECOVER_BY_TABLE meta-function. Do not disable recovery by table.	Server	8.0.1
Column `rebalance_projections_status.duration_sec`	Server	8.0
HDFS Connector	Server	8.0	9.0
Prejoin projections	Server	8.0	9.2
Administration Tools option `--compat21`	Server	7.2.1
admin_tools -t config_nodes	Server	7.2	11.0.1
Projection buddies with inconsistent sort order	Server	7.2	9.0
backup.sh	Server	7.2	9.0
restore.sh	Server	7.2	9.0
copy_vertica_database.sh	Server	7.2
JavaClassPathForUDx configuration parameter	Server	7.1
ADD_LOCATION meta-function	Server	7.1
bwlimit configuration parameter	Server	7.1	9.0
vbr configuration parameters retryCount and retryDelay	Server	7.1	11.0
EXECUTION_ENGINE_PROFILE counters: file handles, memory allocated	Server	7.0	9.3
EXECUTION_ENGINE_PROFILES counter memory reserved	Server	7.0
MERGE_PARTITIONS() meta-function	Server	7.0
krb5 client authentication method Note Use the Kerberos gss method for client authentication, instead of krb5.	All clients	7.0
range-segmentation-clause	Server	6.1.1	9.2
`scope` parameter of meta-function CLEAR_PROFILING	Server	6.1
Projection creation type IMPLEMENT_TEMP_DESIGN	Server, clients	6.1

4 - Eon Mode

New features for Eon Mode

Multiple communal storage locations

Eon Mode databases now support multiple communal storage locations. You can add communal storage locations to your database with the CREATE LOCATION function, and then use the SET_OBJECT_STORAGE_POLICY function to assign database objects to one of the storage locations.

In-database restore points

In-database restore points are lightweight, copy-free backups for Eon Mode databases that enable you to roll back a database to the state at which a restore point was saved. Unlike vbr-based backups, restore points are stored in-database and do not require additional data copies to be stored externally, which results in fast restore point creation and low storage overhead. For more information about in-db restore points, see In-DB restore points.

5 - New and changed in Vertica 24.4

New features and changes in Vertica 24.4.

5.1 - Health Watchdog

Health Watchdog is an automated mechanism that detects and block queries during bad health conditions on the server.

Health Watchdog

A Health Watchdog has been implemented that automatically detects and blocks queries during bad health conditions on ther server. For more details on Heal Watchdog, see Health Watchdog.

5.2 - Upgrading Vertica on Kubernetes

The operator automates Vertica server version upgrades for a custom resource (CR).

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.

5.3 - Sandboxing on Kubernetes

Sandboxing on Kubernetes allows you to create isolated testing environments without the need to set up a new database or reload data, making it easier to test Vertica features in new versions.

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

5.4 - Save restore points from Kubernetes

Enables you to save a restore point from Kubernetes

Save restore points using VerticaDB Operator

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.