10.0.x Release Notes

Vertica
Software Version: 10.0.x

IMPORTANT: Vertica for SQL on Hadoop Storage Limit

Vertica for SQL on Hadoop is licensed per node, on an unlimited number of central processing units or CPUs and an unlimited number of users. Vertica for SQL on Hadoop is for deployment on Hadoop nodes. Includes 1 TB of Vertica ROS formatted data on HDFS.

This 1 TB of ROS limit enforcement is currently only contractual, but it will begin to be technically enforced in Vertica 10.1. Starting with Vertica 10.1, if you are using Vertica for SQL on Hadoop, you will not be able to load more than 1 TB of ROS data into your Vertica database. If you were unaware of this limitation and already have more than 1 TB of ROS data in your database at this time, please make any necessary adjustments to stay below the limit, or contact our sales team to explore other licensing options.

IMPORTANT: Before Upgrading: Identify and Remove Unsupported Projections

With version 9.2, Vertica has removed support for pre-join and range segmentation projections. If a table's only superprojection is one of these projection types, the projection is regarded as unsafe.

Before upgrading to 9.2 or higher, you are strongly urged to check your database for unsupported projections. If the upgrade encounters these projections, it is liable to fail. You must then revert to the previous installation.

Solution: Run the pre-upgrade script

Vertica has provided a pre-upgrade script that examines your current database and sends to standard output its analysis and recommendations. The script identifies and lists any unsupported projections. If the script finds projection buddies with different SELECT and ORDER BY clauses, it generates a deploy script. Run this script to remedy projections so they comply with system K-safety.

https://www.vertica.com/pre-upgrade-script/

For more information, see Fixing Unsafe Buddy Projections in the Vertica documentation.

Updated: 3/23/2021

About Vertica Release Notes

The Release Notes contain the latest information on new features, changes, fixes, and known issues in Vertica 10.0.x.

They also contain information about issues resolved in:

• Hotfixes
• Service Packs
• Major Releases
• Minor Releases

Downloading Major and Minor Releases, and Service Packs

The Premium Edition of Vertica is available for download at https://support.microfocus.com/downloads/swgrp.html.

The Community Edition of Vertica is available for download at https://www.vertica.com/download/vertica/community-edition.

The documentation is available at https://www.vertica.com/docs/10.1.x/HTML/index.htm.

Downloading Hotfixes

Hotfixes are available to Premium Edition customers only. Contact Vertica support for information on downloading hotfixes.

What's New in Vertica 10.0.1

Take a look at the Vertica 10.0.1 New Features Guide for a complete list of additions and changes introduced in this release.

admintools

--force Option for command_host

The new --force option tells the database to delete any unrecognized files in the data folders on the local node.

Backup, Restore, Recovery, and Replication

Support for an On-Premise S3 Backup in Enterprise Mode

You can now back up an Enterprise Mode database to an on-premises destination that supports the S3 protocol, such as Pure Storage FlashBlades. All vbr tasks for Enterprise Mode databases on AWS S3 are supported.

To perform a backup or restore of an on-premises database, you must set some additional environment variables. The vbr configuration file does not change. For more information, see Configuring Backups to and from S3.

Configuration

S3EnableVirtualAddressing

This parameter configures whether to rewrite S3 URLs to use virtual-hosted paths. For example, if you use AWS, the S3 URLs change to bucketname.s3.amazonaws.com instead of s3.amazonaws.com/bucketname. This configuration setting takes effect only when you have specified a value for AWSEndpoint.

Data Types

Casting Arrays and Sets

You can now cast collections (ARRAY and SET). Casting a collection casts each element of the collection, following the same rules as for casts of scalar values.

You can perform explicit casts, but not implicit casts, between arrays and sets. When casting an array to a set, Vertica first casts each element and then sorts the set and removes duplicates.

Casting from a smaller data type to a larger one could cause a collection value to exceed the column limit, causing the operation to fail. For example, if you cast an array of INT to an array of VARCHAR(50), each element takes more space and thus the whole array takes more space.

Comparing and Ordering Collections

You can now compare collections (arrays and sets) using comparison operators (=, <>, <, >, <=, >=), and queries can now compare collections. You can now use collections in the following ways:

• As the grouping column in a GROUP BY Clause.
• As the sort key in an ORDER BY Clause in a query, in an OVER clause (see Window Partitioning), or in a CREATE PROJECTION statement.
• As the sort key in the PARTITION BY part of an OVER clause.
• As a JOIN key (see Joined-Table).

See the "Functions and Operators" section on the ARRAY reference page for information on how Vertica orders collections. (The same information is also on the SET reference page.)

Using Structs in Subqueries and Views

You can now use structs and fields from structs, represented by the ROW data type, in views and subqueries.

Eon Mode

Subcluster Support

The meta-function CLEAR_DATA_DEPOT can now clear data from the depot of a single subcluster.

Subcluster Support for Large Cluster

The large cluster feature addresses the limitations in the Spread service that Vertica uses for cluster-wide broadcast messages. When large cluster is enabled, a subset of nodes, called control nodes, connect to the Spread service. Other nodes depend on control nodes to receive and send these broadcast messages.

In previous versions of Vertica, a control node and the nodes that depend on it were not guaranteed to be within the same subcluster. This cross-subcluster dependency could result in nodes in other subclusters failing when you shut down the subcluster containing their control node.

Now, Vertica always assigns nodes to a control node within their subcluster. When large cluster is enabled, every subcluster must have at least one control node. In Eon Mode, you now set the number of control nodes on a per-subcluster basis, rather than setting a single value for the entire cluster. The control-node related functions SET_CONTROL_SET_SIZE and REALIGN_CONTROL_NODES functions now take a mandatory subcluster argument when in Eon Mode.

Note: These changes do not alter how large cluster works when running in Enterprise Mode. You still set a single cluster-wide value for the number of control nodes in your database.

See Large Cluster for more information.

Important: Upgrading from a prior version of Vertica to version 10.0.1 or beyond does not change the existing layout of control nodes and their dependents in your database. If you have an Eon Mode database with multiple subclusters and have large cluster enabled, your existing control node assignments may cross subcluster boundaries. Vertica highly recommends that you remove these cross-subcluster dependencies. You must realign the control nodes and then restart the subclusters after you upgrade. See Realigning Control Nodes and Reloading Spread for instructions.

Node Subscriptions to Shards is More Deterministic

In previous versions of Vertica, the primary subscriber for a shard was chosen by several different mechanisms, which eventually could result in a random set of shard assignments in a subcluster. Starting in 10.0.1, Vertica assigns shard subscriptions to nodes using a single, simplified process.

As part of this process, one subscriber to each shard is designated as the participating primary node. This node is the only one that reads from and writes to communal storage for the shard. Other nodes in the subcluster that subscribe to the same shard get their data from the primary participating node via peer-to-peer transfer. A new column named IS_PARTICIPATING_PRIMARY in the V_CATALOG.NODE_SUBSCRIPTIONS indicates when a node is the participating primary node for a shard.

Subcluster-level Resource Pools

You can now create and manage resource pools at the subcluster level. In the subcluster-specific resource pools, you can override MEMORYSIZE, MAXMEMORYSIZE, and MAXQUERYMEMORYSIZE settings for built-in global resource pools for that subcluster. A new system table named SUBCLUSTER_RESOURCE_POOL_OVERRIDES lets you examine the overrides applied to global resource pools for a subcluster. Additionally, the RESOURCE_POOLS system table has two new columns named SUBCLUSTER_OID and SUBCLUSTER_NAME. These columns are populated when a resource pool belongs to a specific subcluster.

See Managing Workloads for more information.

Loading Data

Delimited Parser Supports Collections

The default (DELIMITED) parser now supports one-dimensional collections (arrays or sets) of scalar types. Several new COPY options allow customization of delimiters and other special characters. See Loading Delimited Data and the DELIMITED (Parser) reference page.

Security and Authentication

CONNECT TO Vertica: SHA-512 Support

The CONNECT TO VERTICA function now supports SHA-512 as an authentication method.

In-Database Cryptographic Key and Certificate Management

You can now generate or import cryptographic keys and certificates with the CREATE KEY and CREATE CERTIFICATE statements.

For examples, see Generating TLS Certificates and Keys.

MIT Kerberos 1.18.2

MIT Kerberos has been upgraded to version 1.18.2.

SQL Functions and Statements

Exporting Arrays to Parquet

EXPORT TO PARQUET can now export one-dimensional arrays. Nested (multi-dimensional) arrays cannot be exported, though you can extract the nested arrays as one-dimensional arrays and then export them.

Privilege Management for Subcluster Resource Pools

You can now GRANT and REVOKE USAGE privileges on subcluster resource pools.

System Tables

CRYPTOGRAPHIC_KEYS and CERTIFICATES

The new CRYPTOGRAPHIC_KEYS and CERTIFICATES tables contain information about keys and certificates generated or imported through the CREATE KEY and CREATE CERTIFICATE statements.

User-Defined Extensions

C++ UDL Support for Fenced Mode

Vertica user-defined load functions now support fenced mode for source, filter, and parser functions created in C++. Fenced mode allows you to run your UDx code outside of the main Vertica process. This protects the main Vertica process from any issues or crashes in the UDx code that might result in system-wide problems, including database failure.

What's Deprecated in Vertica 10.0.1

This section describes the two phases Vertica follows to retire Vertica functionality:

• 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. Documentation that describes this functionality is removed, but remains in previous documentation versions.

Deprecated

The following Vertica functionality was deprecated and will be retired in future versions:

Removed

The following functionality is no longer accessible as of the releases noted:

Vertica 10.0.1-10: Resolved Issues

Release Date: 3/23/2021

This hotfix addresses the issues below.

Vertica 10.0.1-9: Resolved Issues

Release Date: 3/9/2021

This hotfix addresses the issues below.

Vertica 10.0.1-8: Resolved Issues

Release Date: 2/19/2021

This hotfix addresses the issues below.

Vertica 10.0.1-7: Resolved Issues

Release Date: 2/1/2021

This hotfix addresses the issues below.

Vertica 10.0.1-6: Resolved Issues

Release Date: 12/18/2020

This hotfix was internal to Vertica.

Vertica 10.0.1-5: Resolved Issues

Release Date: 12/8/2020

This hotfix addresses the issues below.

CASE expression

WHEN comparand THEN result
 
...
 
[ ELSE result ]

END

Vertica 10.0.1-4: Resolved Issues

Release Date: 11/12/2020

This hotfix addresses the issues below.

Vertica 10.0.1-3: Resolved Issues

Release Date: 10/28/2020

This hotfix addresses the issues below.

Vertica 10.0.1-2: Resolved Issues

Release Date: 10/7/2020

This hotfix addresses the issues below.

Vertica 10.0.1-1: Resolved Issues

Release Date: 9/23/2020

This hotfix addresses the issues below.

Vertica 10.0.1: Resolved Issues

Release Date: 8/19/2020

This release addresses the issues below.

Known issues Vertica 10.0.1

Updated: 8/19/20

Vertica makes every attempt to provide you with an up-to-date list of significant known issues in each release. We will update this list as we resolve issues and as we learn of new issues.

What's New in Vertica 10.0

Take a look at the Vertica 10.0 New Features Guide for a complete list of additions and changes introduced in this release.

admintools

Eon Mode: list_db

The admintools list_db tool now shows the communal storage location for Eon Mode databases.

Apache Kafka Integration

Vertica 10.0.0 changes some of the default settings in the Apache Kafka integration to support better performance overall and to account for the removal of the WOS.

Longer Default Frame Length

The default frame length is now 5 minutes (increased from the previous default of 10 seconds). This increase helps prevent the creation of many small ROS containers now that Vertica no longer uses the WOS. It is also a better choice for most use cases. The old default frame duration is too short for most non-trivial workloads.

The vkconfig tool now displays a warning if you set the frame duration so low that the scheduler will have less than two seconds to run each microbatch on average. Usually, you should set the frame duration to allow more than two seconds per microbatch.

Default Kafka Resource Pool Change

Prior to 10.0, if you did not assign your scheduler a resource pool, it would use a resource pool named kafka_default_pool. This behavior could cause resource issues if you created multiple schedulers that used the default pool. You could also see problems if your scheduler needed more resources than those provided by the default pool.

In Vertica version 10.0, if you do not specify a resource pool for your scheduler, it will use one quarter of the resources of the GENERAL resource pool. This behavior avoids having multiple schedulers use a single resource pool that has not configured with that workload in mind. This change only affects newly-created schedulers. It does not affect existing schedulers that use the kafka_default_pool.

Configuration

User-Level Configuration Parameters

Vertica now supports setting some configuration parameters for individual users. This support includes expanded syntax for ALTER USER, and new statement SHOW USER.

Database Designer

Database Designer (DBD) has been extensively overhauled. Significant improvements include:

• Optimized resource usage: DBD no longer requires table and catalog locks. It also no longer writes intermediate results such as tentative encodings to disk; instead, it stores transient output in memory. DBD's demands on resources are now so reduced that it can run on a production server with minimal impact on normal operations. Eon Mode users especially benefit from in-memory processing, as it eliminates frequent and expensive writes to communal storage.
• Simplified API: Previously, creating and deploying a design required calls to multiple meta‑functions in a set order. DBD's complex design workflow, combined with its demands on system resources, posed significant deterrents to iterative optimization. Now, a single call to the new DBD meta‑function DESIGNER_SINGLE_RUN can cover the entire design process. The meta-function iterates over all queries within a specified timespan, and returns with a design ready for deployment.

Supported Data Types

Native Support for Arrays and Sets

Vertica-managed tables now support one-dimensional arrays of primitive types. External tables continue to support multi-dimensional arrays. The two types are the same with respect to queries and array functions, but are different types with different OIDs. For more information, see the ARRAY type .

Vertica-managed tables now support sets, which are collections of unique values. For more information, see the SET type.

Several functions that previously operated only on arrays now also operate on sets, and some new functions have been added. For more information, see Collection Functions.

Flexible Complex Types in External Tables

In some cases, the complex types in a Parquet file are structured such that you cannot fully describe their structure in a table definition. For example, a row (struct) can contain other rows but not arrays or maps, and an array can contain other arrays but not other types. A deeply-nested set of structs could exceed the nesting limit for an external table.

In other cases, you could fully describe the structure in a table definition but might prefer not to. For example, if the data contains a struct with a very large number of fields, and in your queries you will only read a few of them, you might prefer to not have to enumerate them all individually. And if the data file's schema is still evolving and the type definitions might change, you might prefer not to fully define, and thus have to update, the complete structure.

Flexible complex types allow you to treat a complex type in a Parquet file as unstructured data in an external table. The data is treated like the data in a flex table, and you can use the same mapping functions to extract values from it that are available for flex tables.

Documentation Updates

Reorganized Documentation on Data Load and Export

Documentation on bulk-loading data (including using external tables), importing or exporting between Vertica databases, and exporting data to Parquet format has been reorganized and improved. See the following new top-level topic hierarchies:

• Getting Data into Vertica
• Exporting Data

Eon Mode

Eon Mode Support for Google Cloud Platform (GCP)

You can now deploy an Eon Mode database on Google Cloud Platform.

Currently, there are a few limitations when using an Eon Mode database on GCP:

• The Google Marketplace Launcher for Eon Mode cannot deploy both the MC and a database cluster. Instead, it creates an MC instance. You use this instance to deploy an Eon Mode database.
• The MC does not support provisioning additional database nodes. A workaround is to provision more nodes than your immediate needs, and then stop them down. Start them again when you need additional nodes.

Future releases will address these limitations.

For more information, see Eon Mode Databases on GCP.

Eon Mode Support for HDFS

Vertica now supports communal storage on HDFS when accessed through WebHDFS. See Installing Eon Mode on Premises with Communal Storage on HDFS for more information.

There are some restrictions:

• Vertica does not support the MapR distribution of HDFS, which is accessed through an NFS mount point and not through WebHDFS, for communal storage.
• Vertica does not support the use of Vertica MC or admintools to administer data located on HDFS.
• The vbr backup and restore utility is not currently supported for communal storage on HDFS.

Pinning on Subclusters

Vertica now supports pinning on subcluster depots. This enhancement is implemented with two new meta-functions, which supersede the now-deprecated SET_DEPOT_PIN_POLICY meta-function:

• SET_DEPOT_PIN_POLICY_TABLE
• SET_DEPOT_PIN_POLICY_PARTITION

New DelayForDeletes Configuration Parameter Setting and Default Value

The new default value for DelayForDeletes is 0, which deletes a file from communal storage as soon as it is not in use by shard subscribers. In earlier releases, the default was 2 hours.

After you upgrade, DelayForDeletes retains any value that you configured in a previous version, although Vertica recommends setting this configuration parameter to 0 for version 10.0.0. If you used the previous default of 2 hours, DelayForDeletes is set to 0 automatically.

Nodes Now Always Warm Their Depots in the Background

When depot warming is enabled, newly added, restarted, or recovered nodes now warm their depots in the background. They start processing queries immediately. They also copy data from communal storage to populate their depots with relevant data based on the content of other node's depots in their subcluster.

Previously, nodes defaulted to foreground depot warming: when starting, they would copy relevant data from communal storage into their depots before taking part in queries. This behavior could lead to a delay between the time you added nodes to a subcluster and when they assisted in resolving queries.

This new behavior is the default. Depot warming in the foreground is no longer supported.

The BACKGROUND_DEPOT_WARMING function is now deprecated. This function had nodes switch from foreground to background depot warming. It has been deprecated and will be removed in a future release.

Voltage SecureData Integration

Type Casting and Identity Management with SQL Macros

You can integrate the VoltageSecureProtect and VoltageSecureAccess functions with SQL macros to manage identities and perform automatic type casting.

Voltage SecureData SimpleAPI 6.0

The version 6.0 of the SimpleAPI library includes several new features.

NULL Value Handling

When given a NULL value, VoltageSecureProtect now returns a NULL value. Previously, NULL inputs would return an error.

Configurable Network Timeout

You can now configure the network timeout for when Vertica interacts with your Voltage SecureData server.

The default and maximum value for this parameter is 300 seconds.

Manually Refresh Client Policy

You can now manually refresh the client policy across all nodes with the VoltageSecureRefreshPolicy function.

Safe Unicode FPE Formats

VoltageSecureProtect and VoltageSecureAccess now offer predefined formats to encrypt and decrypt all Unicode code point values. Previous versions of the Voltage library offered incomplete Unicode support with predefined formats using FPE extensions (FPE2 and JapaneseFPE).

For more information, see Best Practices for Safe Unicode FPE.

Machine Learning

Support for PMML Models

Vertica now supports the import and export of K-means, linear regression, and logistic regression machine learning models in Predictive Model Markup Language (PMML) format. Support for this platform-independent model format allows you to use models trained on other platforms to predict on data stored in your Vertica database. You can also use Vertica as your model repository.

The PREDICT_PMML function is new in Vertica 10.0. In addition, these existing functions now support PMML models:

• IMPORT_MODELS
• EXPORT_MODELS
• GET_MODEL_ATTRIBUTES
• GET_MODEL_SUMMARY

Support for TensorFlow Models

Vertica now supports importing trained TensorFlow models, and using those models to do prediction in Vertica on data Stored in the Vertica database. Vertica supports TensorFlow models trained in TensorFlow version 1.15.0.

The PREDICT_TENSORFLOW function is new in Vertica 10.0. In addition, these existing functions now support TensorFlow models:

• IMPORT_MODELS
• EXPORT_MODELS
• GET_MODEL_ATTRIBUTES
• GET_MODEL_SUMMARY

Management Console

Provision and Revive Eon Clusters on GCP

Management Console (MC) now supports provisioning and reviving Eon database clusters on Google Cloud Platform (GCP).

Create and Manage Eon Mode Subclusters

In addition to monitoring Eon Mode subclusters, MC now allows you to create and manage subclusters for Eon Mode on AWS and Eon Mode for Pure Storage.

Depot Management Tools: Depot Efficiency and Depot Pinning

Depot Efficiency

The new Depot Efficiency tab on the MC Database > Depot Activity Monitoring page provides charts with metrics that allow you to determine whether your Eon depot is properly tuned and whether there are issues you need to adjust for better query performance.

Depot Pinning

The new Depot Pinning tab on the MC Database > Depot Activity Monitoring page allows you to view the tables that are pinned in the depot. It also allows you to create, modify, and remove the pinning policies for each table. You may want to change pinning policies based on factors such as a table's frequency of re-fetches, the size of a table's data in depot, and the number of requests for a table's data.

Vertica in Eon Mode for Pure Storage

MC now supports Vertica in Eon Mode for Pure Storage, including creating and reviving Eon Mode databases on-premises, using Pure Storage FlashBlade as the communal storage.

Select and Execute Workload Analyzer Recommendations

In MC, in addition to viewing Workload Analyzer (WLA) tuning recommendations, you can also select and execute certain individual WLA tuning commands, to improve how queries execute on your database.

Set the MAXQUERYMEMORYSIZE Parameter from MC

The parameter "MAXQUERYMEMORYSIZE" was added in version 9.1.1, with the ability to modify the parameter using VSQL.

In 10.0, you can now modify the "MAXQUERYMEMORYSIZE" parameter directly from MC.

Projections

Changing Projection Column Encodings

You can now call ALTER TABLE…ALTER COLUMN to add an encoding type to a projection column, or change its current encoding type. Encoding projection columns can help reduce their storage footprint, and enhance performance. Until now, you could not add encoding types to an existing projection; instead, you had to recreate the projection and refresh its data. Doing so for very large projections was liable to incur significant overhead, which could be prohibitively expensive for a running production server.

When you add or change a column's encoding type, it has no immediate effect on existing projection data. Vertica applies the encoding only to newly loaded data, and to existing data on mergeout.

Security and Authentication

New Parameter: LDAPLinkJoinAttr

The attribute used to associate users and groups can vary between standards. For example, POSIX groups use the memberUid attribute. To provide support for these standards, the LDAPLinkJoinAttr parameter allows you to specify the attribute with which to associate users to their roles in the LDAP Link.

For more information on this and other parameters, see LDAP Link Parameters.

KERBEROS_CONFIG_CHECK: Credential Cache Files

To help with troubleshooting, KERBEROS_CONFIG_CHECK now prints the path of KerberosCredentialCache files.

SQL Functions and Statements

Some Array Functions Renamed

The array_min, array_max, array_sum, array_avg, array_count, and array_length functions perform aggregate operations on the elements of an array. They have been expanded to operate on other collection types and have been renamed to apply_min, apply_max, apply_sum, apply_avg, apply_count_elements, and apply_length. The array_* functions are deprecated and automatically call the corresponding apply_* functions. For more information, see Collection Functions.

SQL Support for User-Level Configuration

Two SQL statements support setting configuration parameters for individual users:

ALTER USER now supports setting user-level configuration parameters for the specified user.

New statement SHOW USER returns all configuration parameter values that are set for the specified user.

New EXPLODE Array Function

The new EXPLODE array function expands a 1D array column and returns query results where each row is an array element. The query results include a position column for the array element index, and a value column for the array element.

Statistics

Statistics Collection Improvements

Statistics that are collected for a given range of partition keys now supersede statistics that were previously collected for a subset of that range. For details, see Collecting Partition Statistics.

System Tables

New system table V_MONITOR.TABLE_STATISTICS

TABLE_STATISTICS displays statistics that have been collected for tables and their respective partitions.

New column in RESOURCE_POOL_STATUS

RESOURCE_POOL_STATUS now includes a RUNTIMECAP_IN_SECONDS column, which specifies in seconds the maximum time a query in the pool can execute. If a query exceeds this setting, it tries to cascade to a secondary pool.

Users and Privileges

Increased Security for Privileges through Non-Default Roles

The Vertica database is now more strict with privileges through non-default roles. Some actions have privilege requirements that depend on the effective privileges of other users. If these other users have the prerequisite privileges exclusively through a role, the role must be a default role for the action to succeed.

For example, for Naomi to change Zinn's default resource pool to RP, Zinn must already have USAGE privileges on RP. If Zinn only has USAGE privileges on RP through the Historian role, it must be set as a default role, otherwise the action will fail.

For more information on changing a user's default roles, see Enabling Roles Automatically.

Removal of Support for Write-Only Storage (WOS)

Over the past several releases, Vertica has significantly improved small batch loading into ROS, which now provides WOS-equivalent performance. In order to simplify product usage, Vertica began in release 9.3.0 to phase out support for WOS-related functionality. With Vertica 10.0, this process is complete; support for all WOS-related functionality has been removed.

What's Deprecated in Vertica 10.0

This section describes the two phases Vertica follows to retire Vertica functionality:

• 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. Documentation that describes this functionality is removed, but remains in previous documentation versions.

Deprecated

The following Vertica functionality was deprecated and will be retired in future versions:

Removed

The following functionality is no longer accessible as of the releases noted:

For more information see Deprecated and Retired Functionality in the Vertica documentation.

Vertica 10.0.0-3: Resolved Issues

Release Date: 7/29/2020

This hotfix addresses the issues below.

Vertica 10.0.0-2: Resolved Issues

Release Date: 6/24/2020

This hotfix addresses the issues below.

Vertica 10.0.0-1: Resolved Issues

Release Date: 6/1/2020

This hotfix addresses the issues below.

Vertica 10.0.0: Resolved Issues

Release Date: 5/7/2020

This release addresses the issues below.

Known issues Vertica 10.0.0

Updated: 5/7/20

Vertica makes every attempt to provide you with an up-to-date list of significant known issues in each release. We will update this list as we resolve issues and as we learn of new issues.