Release Notes

Software Version: 8.1.x


Updated: June 8, 2017


About Vertica Release Notes

What's New in Vertica 8.1

Security Warnings

Vertica 8.1.0-4: Resolved Issues

Vertica 8.1.0-3: Resolved Issues

Vertica 8.1.0-2: Resolved Issues

Vertica 8.1.0-1: Resolved Issues

Vertica 8.1: Resolved Issues

Vertica 8.1.x: Known Issues

About Vertica Release Notes

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

They also contain information about issues resolved in:

Downloading Major and Minor Releases, and Service Packs

The Premium Edition of Vertica is available for download at

The Community Edition of Vertica is available for download at the following sites:

The documentation is available at

Downloading Hotfixes

Hotfixes are available to Premium Edition customers only. Each software package on the site is labeled with its latest hotfix version.

What's New in Vertica 8.1

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

Flattened Tables

Highly normalized database designs can incur significant query overhead; however, maintaining an additional redundant denormalized schema for query performance has its own administrative costs. Vertica now includes flattened tables to address this issue. Flattened tables include columns that get their values by querying other tables. Operations on the source tables and flattened table are decoupled; changes in one are not automatically propagated to the other. This minimizes the overhead that is otherwise typical of denormalized tables.

See more: Query Optimization

Kafka Schema Registry Support

Vertica now supports the use of a Confluent schema registry with the KafkaAVROParser. By using a schema registry, you enable the Avro parser to parse and decode messages written by the registry and to retrieve schemas stored in the registry. In addition, a schema registry enables Vertica to process streamed data without sending a copy of the schema with each record.

See more: Apache Kafka Integration

Kafka Execution Parallelism

The Apache Kafka integration uses User Define Source and COPY commands to load data directly from Kafka topics to Vertica tables. You can now specify the executionparallelism parameter in the KafkaSource UDL. You can use this parameter to throttle the number of threads used to process any COPY statement. It also increases the throughput of short queries issued in the pool, especially if the queries are executed concurrently.

See more: Apache Kafka Integration

Create a Flex Tables from Query Results

The CREATE FLEX TABLE AS statement now allows you to create a flex table from the results of a query.

See more: Creating a Flex Table from Query Results

Spark 2.0 Support

The Vertica Connector for Apache Spark now supports Spark 2.0. Spark 2.0 provides API stability, SQL 2003 support, subquery support, improved ORC and Parquet performance, and unification of data frame with data sets.

See more: Apache Spark Integration

Compute Approximate Percentile

Exact median and exact percentile functions may be slow for extremely large data, because the function must perform a full table scan to calculate exact values. You can now use the aggregate function APPROXIMATE_PERCENTILE to compute approximate percentiles on large data sets. Based on the T-digest algorithm, this function works for looking for patterns in data, while remaining faster and using less memory than the exact percentile function.


Sample BI Tools with Vertica on AWS

With Vertica on AWS, sample Tableau and Logi workbooks. These workbooks come pre-built with example clickstream data to illustrate how Vertica analysis improves digital marketing.

See more: AWS Marketplace

Security Warnings

A critical security vulnerability has been found. An unauthenticated entity with the ability to establish a connection to the client socket can reset the password of a known database user. This security vulnerability has been resolved in 8.1.0-1. Vertica strongly recommends you upgrade to this version as soon as possible.

Vertica 8.1.0-4: Resolved Issues

Release Date: 6/8/2017

This hotfix addresses the issues below.




VER-54401 Admin Tools This fix resolves an issue that occurred when setting parameter MaxParsedQuerySizeMB.



This fix improves the performance of APPROXIMATE_MEDIAN and APPROXIMATE_PERCENTILE when using GROUP BY.



Restoring objects containing grouped ROSes previously failed.


DDL - Projection

With this fix, dropping a primary key constraint also drops the supporting key constraint projections, if they are no longer necessary.


Execution Engine

Previously, if ephemeral or execute nodes were present in your cluster, Vertica incorrectly created many unnecessary key constraint projections.


Execution Engine

The datatype of the column VIEW_DEFINITION in system table v_catalog.views has been changed from varchar(65000) to varchar(32000).



Moving flex tables did not also move their corresponding key projections and views.


Kafka Integration

The Kafka data source did not correctly handle an error that occurred during loading or parsing by the KafkaAVROParser. This sometimes caused the Vertica process to fail. With this fix, the load fails appropriately if the error occurs.


Kafka Integration

The Kafka scheduler did not work if the database had a non-default locale. The scheduler now explicitly sets the locale to the Vertica default locale.


Kafka Integration

The Kafka scheduler logger incorrectly attempted to insert log messages into the kafka_events system table under the default config schema, even if a user specified a different schema.



Queries with multiple distinct aggregates grouped on a subquery containing another subquery sometimes caused the server to fail.


Catalog Engine, ResourceManager

During recovery, if acquiring a global catalog lock failed on some nodes, the nodes sometimes panicked and aborted recovery.
VER-54591 Security This fix resolves an issue that sometimes caused the database to fail during LDAP authentication.



A performance issue with variable length types used as intermediates of User Defined Aggregates has been fixed.


UI - Management Console

In Management Console, non-superusers were unable to upload queries to the database designer. In addition to this fix, administrators can now adjust the number of queries that a non-superuser can include in the file to be uploaded to the design. The default value is 50. To change the limit, open the file /opt/vconsole/config/, and edit the following parameter: dbd.nonadminuser.fileupload.queries.limit


Optimizer, Usability

CREATE TABLE AS statements that included non-stable functions occasionally failed with the following error: "Cannot use meta function or non-deterministic function in SEGMENTED BY expression"

Vertica 8.1.0-3: Resolved Issues

Release Date: 5/17/2017

This hotfix addresses the issues below.






This fix removes an incorrect warning message during vbr replication.



When backing up to shared storage, it was possible for vbr to treat the same actual location on a shared volume as different backup locations, which could result in backup failure when trying to delete the same file multiple times.


Client Drivers - JDBC

If JDBC received multiple warnings while running routable queries, the JDBC client sometimes hung.


DDL - Projection

Vertica prefixed the table name in projections created as part of a CREATE TABLE AS statement. Vertica no longer does so if the target schema of the statement is different from the schema of the source table.



Including a predicate when querying ORC files in an evolved schema caused the database to fail.


Installation Program

After Vertica upgrades, pre-existing storage IDs are updated the first time a backup occurs. After an upgrade to Vertica version 7.2.x or above, database failure or data corruption sometimes occurred if a storage ID upgrade happened simultaneously to a data management operation, such as repartition or mergeout.


UI - Management Console

In rare circumstances, Management Console did not load the Database Designer page and instead displayed a "String index out of range" error.

Vertica 8.1.0-2: Resolved Issues

Release Date: 5/1/2017

This hotfix addresses the issues below.




VER-53212 AP-Advanced The function KMEANS failed to generate an output view in custom schemas.
VER-53380 AP-Geospatial This hotfix resolves an issue in the function ST_Distance that caused segmentation fault.



ST_Distance and STV_DWithin sometimes encountered errors on a large table that caused the server to fail. This hotfix puts ST_Distance and STV_DWithin in fenced mode to prevent server failure.


Data Removal - Delete, Purge, Partitioning

If Vertica dropped a table after taking an O lock during a partition swapping operation, a segmentation fault occurred when Vertica re-checked the table.


Database Designer Core

Running Database Designer on tables that had multiple enabled constraints on the same sets of columns sometimes produced inappropriate projection layouts.


Error Handling

This fix resolves an issue in which the server sometimes silently exited after a log rotate.


Data load / COPY Hadoop

Previously, predicate pushdown in the Parquet and ORC parser did not support predicates that used IN / NOT IN clauses. This fix adds support.


Kafka Integration

Due to a race condition in the librdkafka library, a partially destroyed topic object was used when loading topic metadata and caused Vertica to fail. This fix moves a read-write lock to prevent this condition from occurring.



If Vertica attempted to recover a table with out-of-date projections after a partition swapping operation, Vertica incorrectly dropped ROSes in the swapped partition, causing projection row count mismatch.

Vertica 8.1.0-1: Resolved Issues

Release Date: 4/17/2017

Vertica has introduced hotfix 8.1.0-1 to address a security vulnerability. Vertica strongly recommends you upgrade to this version as soon as possible.

This hotfix addresses the issue below.





Security, Virtual Appliance

A critical security vulnerability has been found in Vertica. An unauthenticated entity with the ability to establish a connection to the client socket can reset the password of a known database user. This security vulnerability has been resolved.

Vertica 8.1: Resolved Issues

Release Date: 4/13/2017

To see a complete list of additions and changes introduced in this release, refer to the Vertica 8.1.x New Features Guide.





Admin Tools

In rare cases, admintools timed out when adding new nodes to a cluster.



The table dc_backups now includes the column snapshot_type. This column indicates whether reported backup activity was a backup or a copycluster.



Vertica sometimes reassigned ownership of objects incorrectly when restoring or replicating tables in CreateOrReplace mode.



When backing up to shared storage, it was possible for vbr to treat the same actual location on a shared volume as different backup locations, which could cause corrupt backup files.



Object replication and restore sometimes failed if the target database had storage locations, UDTs or storage policies with the same object IDs as the source database objects.



You can query tables without their fully qualified names (i.e schema.table) by setting the search_path. Such queries sometimes failed if a referenced schema was replicated concurrently.



Vertica 7.2.3-15 and later failed to clean up a temporary directory created during backup.


Catalog Engine

Previously, the view_definition column of the VIEWS system table would truncate definitions that exceeded the 8192 character limit. The limit for the view_definition column has been increased to 65,000 characters.


Client Drivers - ADO

When opening a connection on Windows Server 2012 R2, an error caused a failed connection if permissions were set using domain management.


Client Drivers - JDBC Client Drivers - ODBC

Queries made through JDBC and ODBC incorrectly reported EOL errors for queries containing nested comments. The error did not occur with queries made from vsql.



In the past, when adding multiple nodes to a cluster, Vertica invited them to the cluster one at a time. Now Vertica invites all available nodes at once.



Running the database designer to optimize a table with a large number of projections while simultaneously dropping the table could result in a node failing with a fatal SIGSEGV signal.



Occasionally, Vertica would issue an error if you tried to drop a partition on a table that included a text index.



A CREATE TABLE statement with a LIKE clause INCLUDING PROJECTIONS would roll back if the source table included table-qualified field names (table.field) within a check constraint predicate.


DDL Data Removal - Delete, Purge, Partitioning

Querying a table while performing data changing operations on it could produce incorrect results, due to inconsistent snapshots across nodes.


Data Removal - Delete, Purge, Partitioning

Vertica incorrectly summarized the data from the v_monitor.PARTITIONS view and the v_monitor.PARTITION_COLUMNS view due to an incorrect join occurring with delete vectors.


Data load / COPY

When using apportioned load, Vertica could read one row incorrectly if a portion ended with an escape character and the next began with a record terminator. Built-in parsers now account for this case.


Data load / COPY

Non-dbadmin users could not create a rejected data table using COPY if the path to the rejected records file contained a symbolic link.


Data load / COPY

When loading data with multi-character record terminators while using apportioned load, Vertica could drop up to one record per portion. A row was lost from a portion if the end of the portion landed on any character of the record terminator other than the last one.


Database Designer Core

Running DESIGNER_DESIGN_PROJECTION_ENCODINGS on projections sometimes caused Vertica to incorrectly remove comments on those projections.



Running scrutinize left behind zombie SSH processes.



Running scrutinize left behind zombie SSH processes.


Execution Engine

During long-running sessions, Vertica sometimes held onto query level resources longer than necessary.


Data load / COPY Execution Engine

INSERT queries with joins running as part of ETL took longer to complete in Vertica 7.2.3.
VER-49641 Execution Engine

Exporting data from one Vertica database to another using the EXPORT TO VERTICA statement sometimes failed if the destination table included an enabled primary key or unique constraint. Vertica produced an error message similar to the following: “Client Server protocol error. Message type 'ServerInfo' is invalid in state 'CommandDone'.”


Execution Engine

DataReader's getVal method occasionally caused SIGSEGV failures due to int overflows.


Execution Engine

If a commit transaction failed while AUTOCOMMIT was enabled, in some cases Vertica did not clean up constraints enforcement objects. This could cause node failure the next time a query successfully ran.


Execution Engine

Inserting a Top-K projection sometimes failed if it contained long varchar columns.



In some cases, flex map functions returned values larger than allowed by their return types. This caused the server to fail.



Previously, Vertica did not check the size of a file immediately after writing it to HDFS, which sometimes caused data consistency issues. With this fix, Vertica produces an error and rolls back the transaction if a file size mismatch occurs.



Parquet files can contain decimal values in INT32 and INT64 columns. Previously, Vertica was not able to read these values and returned an error. Now, Vertica reads them as decimals if the columns in the external tables are defined as decimals.



The move_partitions_to_table function could incorrectly issue the error “A DDL statement interfered with this statement” if the source table included an enabled primary key constraint and schema-qualified table names were passed to the function.


Installation Program

The issue where the machine startup was delayed due to low entropy, Admintools would time-out with a report that the nodes had failed to start has been resolved. Admintools now detects the low-entropy situation and reports the cause of the delay. Entropy accumulates with time, and the entropy-accrual rate can be increased by interacting with the machine.


Kafka Integration

An incorrect assertion within the UDFilter occasionally generated a false error, and in rare cases could cause the database to fail.



Previously, running the command "CONNECT TO VERTICA ... FROM VERTICA" would sometimes return an error: Internal Optimizer Error (11). This issue has been resolved in Release 8.1.


Execution Engine Optimizer

Certain NOT IN anti-join queries failed to spill and threw a run-time error.


Front end - Parse & Analyze Optimizer

Vertica meta-function export_objects now supports table names with embedded commas.



If any nodes were down, queries using predicates on live aggregate projections sometimes failed with an error.



Previously, explain plans could return very inaccurate row estimation for queries that returned unique or nearly unique results due to how selectivity was estimated. This issue is resolved in Release 8.1.



Previously, Vertica always pruned aggregate columns in a subquery if the subquery had no group by expression. This could result in a wrong result. This issue is fixed in Release 8.1.
VER-42209 Execution Engine Optimizer Each WHEN MATCHED and WHEN NOT MATCHED clause in a MERGE statement can now optionally specify an update filter and insert filter, respectively. MERGE supports Oracle-style syntax for specifying these filters.


Execution Engine Optimizer

The database sometimes failed when Vertica set the type modifier incorrectly in certain CASE statements with SQL macros.


Execution Engine Optimizer

Some queries that contained CASE expressions, and ran in a runtime pool with a defined runtime cap and cascading, caused node failure.



Under certain circumstances, involving complex cyclic joins, Vertica encountered an internal optimizer error.


Basics Optimizer

On upgrading to Vertica 8.0.1-0, Vertica merged an anchor table's unsegmented projections under a single identifier. Vertica used a projection's base name to identify duplicates. In some cases, this approach caused changes to the database catalog that prevented the database from restarting. Vertica 8.0.1-1 resolves this issue. Now, on upgrade, Vertica automatically merges unsegmented projections of the same anchor table with identical properties. These properties include but are not exclusive to: * Sort order * Number of columns and their order * Encodings * Identical creation epochs Vertica retains all out-of-date projections. One exception applies: the out-of-date projection is duplicated by another projection that is up to date. In that case, Vertica drops the out-of-date projection.


Optimizer - Query Rewrite

Aggregating CASE expressions of numeric type sometimes caused an internal server error.



When recovering to a specific epoch, Vertica no longer sets the current checkpoint epoch to zero for projections created after the specified epoch.



Previously, rebalance hung if a buddy projection group contained both balanced projections and projections that needed to be rebalanced. Additionally, Vertica generated an internal error if it attempted to perform multiple rebalance tasks on the same projection simultaneously.



In some circumstances, Vertica continually allocated unused virtual memory, which slowed performance. This issue has been resolved.


Data load / COPY SDK

The API did not allow user-defined parsers to enforce a requirement of NOT NULL for a column, so parsers could write null values into these columns. The API now makes this column information available to parsers, and parsers are responsible for complying.



The issue where a user assigned the SYSMONITOR role could not view other user's sessions (SESSIONS table) has been resolved.



The issue where user's passwords were appearing in plain text in the dc_requests_table has been resolved. The passwords are now masked.



The issue where the creation of a second user with the DBADMIN role did not have the same privileges as the original DBADMIN user has been resolved. A new user assigned the DBADMIN role now has the same privileges as the default DBADMIN user.
VER-51644 Sessions During long-running sessions, Vertica sometimes held onto query level resources longer than necessary.


Tuple Mover

Querying a table while performing data changing operations on it could produce incorrect results, due to inconsistent snapshots across nodes.


UI - Management Console

Management Console encountered errors if the operating system language was set to Japanese.


Admin Tools UI - Management Console

With this fix, Management Console accepts 0-100 characters for database passwords.


UI - Management Console

Management Console encountered JavaScript errors on the Overview page if the browser language was set to Japanese.


UI - Management Console

Disabling or enabling a network interface controller sometimes caused errors in Management Console. Such errors included displaying duplicate cluster information, and an incorrect error message stating that the database was running an older version of Vertica.
VER-50768 UI - Management Console Permission checks that took more than 1 minute during Management Console login caused the login page to hang.


UI - Management Console

During email configuration, Management Console previously could not accept empty SMTP credential fields, even if no credentials were necessary.
VER-51388 UI - Management Console The Vertica Agent Rest API returned an incorrect Vertica version number.


UI - Management Console

When a Management Console user that was mapped to a non-dbadmin Vertica user viewed MC charts, MC did not properly close connections to Vertica.


Execution Engine Optimizer

A high-concurrency throughput regression occurred between versions 8.0 and 8.0SP1.

Known issues and limitations in Vertica 8.1.x

Updated: April 13, 2017

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.

Known Limitations

Backup operations are not currently supported on Vertica implementations using HDFS storage locations.

HCatalog connector does not currently support Kerberos authentication. Currently only HDFS Connector supports Kerberos authentication.

Known Issues




VER-47840, VER-47885, VER-47886 AP-Advanced

Upgrading from 7.2.3 to Vertica 8.0 or above can cause naming conflicts due to new UDx names introduced in for Machine Learning in Vertica 8.0.

Two types of conflicts can occur:

a. If a 7.2.3 UDx name conflicts with UDx's introduced in the Vertica 8.0 Machine Learning Package, the Machine Learning Package installation fails when you start the database for the first time after upgrading Vertica. In this case, you can find the reason for failure and name conflict details in the AdminTools log file.

b. If a 7.2.3 UDx name conflicts with Vertica Machine Learning functions introduced in Vertica 8.0, no failure occurs. However, after upgrading, the Vertica 7.2.3 UDx's are not available for execution due to the naming conflict. Vertica 8.0 introduced the following functions:









Workaround: In both cases, rename the UDx causing the conflict and retry the installation.

VER-43040 Client Drivers - ODBC ENABLE_WITH_CLAUSE_MATERIALIZATION is not supported for WITH CLAUSE prepared statements.
VER-42714 Execution Engine

Be aware that if Vertica cancels a query that generated an error, Vertica sometimes additionally generates the error "Send: Connection not open" during the cancel, even though that is not the cause of the original error.

VER-42282 Kafka Integration

In some cases, Vertica fails while loading data from Kafka. The failure is often preceded by an error indicating a discrepancy between the bytes read by the DataBuffer and LengthBuffer.


Enable cooperative parsing with the following command:

ALTER DATABASE <dbname> SET EnableCooperativeParse=0

Cooperative parsing can slow database performance, but decreases the likelihood of a failure.

VER-48062 Security When determining valid ciphers to set on a FIPS-enabled system, be aware that SELECT SET_CONFIG_PARAMETER('EnabledCipherSuites','....'); can accept invalid values. For example, it could accept a cipher suite not allowed by FIPS. However, invalid cipher suites are not present in the FIPS-enabled system, so their algorithms are not used.
VER-48634 UI - Management Console

If there is no database password, it is possible for a database user with no assigned role to shut down the database through Management Console.

Workaround: Assign a password to the database.


Legal Notices


The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice

© Copyright 2006 - 2017 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Send documentation feedback to HPE