Release Notes

Vertica
Software Version: 8.0.x

 

Updated: March 24, 2017

 

About Vertica Release Notes

What's New in Vertica 8.0.1

Vertica 8.0.1-2: Resolved Issues

Vertica 8.0.1-1: Resolved Issues

Vertica 8.0.1: Resolved Issues

Vertica 8.0.0-3: Resolved Issues

Vertica 8.0.0-2: Resolved Issues

Vertica 8.0.0-1: Resolved Issues

Vertica 8.0.0: Resolved Issues

Vertica 8.0.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.0.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 my.vertica.com.

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

The documentation is available at http://my.vertica.com/docs/8.0.x/HTML/index.htm.

Downloading Hotfixes

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

What's New in Vertica 8.0.1

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

Naive Bayes Algorithm

Naïve Bayes is a popular classification algorithm that can be used on huge data sets to perform multiclass predictions. This algorithm is now a Vertica SQL function. You can easily classify large data sets in Vertica using Naïve Bayes algorithm and perform multi-label classification on numerical and categorical data.

See more: Naive Bayes

Management Console in the Vertica Cloud

Management Console is now part of both Vertica offerings on Amazon. You can deploy the MC AMI into a new standard cluster automatically using a Cloud Formation Template, or deploy the MC AMI into a new or existing cluster manually.

See more: MC Amazon Machine Image

Faster Node Recovery and Improved Operation During Node Recovery

Vertica node recovery checks for data consistency and identifies corrupt files. Corrupted files behind the Ancient History Mark slowed recovery while the system removed them. To speed recovery times, Vertica can now report corrupted partitions and give you the opportunity to handle these separately, so the system can quickly focus on the recovery of the good tables.

When the new ApplyEventsDuringSALCheck parameter is enabled, Vertica uses Catalog events to filter out the dropped corrupt partitions during node startup.

See more: Apply Events During SALCheck Parameter

When nodes were down in a K-safe cluster, the Vertica optimizer used to create a modified query plan that took the missing nodes into account. Now, the Vertica Optimizer uses a nodes-down query plan that is the same as with all nodes up, creating less overhead for queries when nodes are down.

See more: Nodes Down Query Plans

HDFS Usability and Scale Improvements

Vertica now supports specifying a Hadoop name node or name service in the hdfs: URI in the COPY FROM statement. With the ability to COPY directly from HDFS, the HDFS connector is not necessary. This new direct access supports Kerberos, apportioned load, failover retry, and HA name node with LibHDFS++. This provides a more reliable connection between HDFS and Vertica even if the name node goes down, and enables Vertica to access data in more than one HDFS cluster.

See more: Direct Access to HDFS and Read from Multiple HDFS Clusters

Leverage Hive style partition pruning with ORC & Parquet readers

Vertica now exposes Hive style partition pruning when you use the ORC and Parquet readers, so you can specify Hive partitions when querying external tables.

See more: Support for Partition Columns in Hadoop Native Formats

Improved Speed and Scalability of in-DB Machine Learning

Machine Learning algorithms are now able to perform computations in memory. At the beginning of algorithm execution, cache the tables in memory for quicker access on subsequent queries. To optimize algorithm performance, you can adjust the amount of memory allocated to the algorithms by adjusting the BLOBDATA resource pool. If a table is too large to fit into memory, it spills to disk, so machine learning algorithms can scale up to any data size.

See more: New Resource Pool for BLOBDATA

Vertica 8.0.1-2: Resolved Issues

Release Date: 3/24/2017

This hotfix addresses the issues that appear below.

Issue

Component

Description

VER-52144 Admin Tools, AP-Advanced Due to renamed UDxs, upgrading the Machine Learning package to Vertica 8.0.1 produced unnecessary errors.
VER-52430 Backup/DR 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.
VER-52130 Backup/DR Vertica sometimes reassigned ownership of objects incorrectly when restoring or replicating tables in CreateOrReplace mode.
VER-52431 Backup/DR 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.
VER-51627 Backup/DR An incorrect assertion sometimes occurred when restoring or replicating SQL UDFs in Create or CreateOrReplace mode.
VER-52434 Basics This fix re-introduces caching system core count to improve throughput.
VER-51336 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.
VER-53002 Data load / COPY Under rare circumstances, if an import/export statement failed, a subsequent one from the same session could commit inconsistent data if a node left the cluster before the statement committed. This sometimes caused count mismatch between buddy projections in the target table.
VER-51887 DDL - Projection Vertica skipped unsegmented projections on global temporary tables during the rebalance process.

VER-51987, VER-51986, VER-52420, VER-51988

Execution Engine During long-running sessions, Vertica sometimes held onto query level resources longer than necessary.
VER-52210 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.
VER-52579 Execution Engine Inserting a Top-K projection sometimes failed if it contained long varchar columns.
VER-50887 Execution Engine Some queries that contained CASE expressions, and ran in a runtime pool with a defined runtime cap and cascading, caused node failure.
VER-51768 Kafka Integration An incorrect assertion within the UDFilter occasionally generated a false error, and in rare cases could cause the database to fail.
VER-51565 Optimizer Some analytic functions not eligible for shared execution were incorrectly grouped into a shared execution group.
VER-51857 Optimizer Under certain circumstances involving complex cyclic joins, Vertica encountered an internal optimizer error.
VER-51584 Tuple Mover Querying a table while performing data changing operations on it could produce incorrect results, due to inconsistent snapshots across nodes.
VER-50020 UI - Management Console Management Console encountered JavaScript errors on the Overview page if the browser language was set to Japanese.

Vertica 8.0.1-1: Resolved Issues

Release Date: 2/8/2016

This hotfix addresses the issues that appear below.

Issue

Component

Description

VER-51070 Backup/DR When designating a shared storage volume for backups, vbr sometimes used a single location for different backups, which could corrupt backup files.
VER-50999 Backup/DR The amount of time required to remove large numbers of ROS files from backups has been significantly improved.
VER-51334, VER-51435 Basics, Optimizer, Catalog Engine

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.

VER-50446 Catalog Engine If a corrupt unpartitioned table was dropped before node restart and ApplyEventsDuringSALCheck was enabled, segmentation fault sometimes occurred during node restart.
VER-50839 Data load / COPY, Execution Engine INSERT queries with joins running as part of ETL took longer to complete in Vertica 8.0.1.

Vertica 8.0.1: Resolved Issues

Release Date: 12/16/2016

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

 

Issue

Component

Description

VER-46993, VER-47599

AP-Geospatial

ST_Intersects incorrectly evaluated some GEOMETRY objects as too complex. This fix improves the evaluation process.

VER-44909

Backup/DR

VBR worker threads now respond more quickly to failures.

VER-45246

Backup/DR

The amount of time required to remove large numbers of ROS files from backups has been significantly improved.

VER-45975

Backup/DR

Replication tasks no longer report files not expected to be present as missing.

VER-48644

Backup/DR

When restoring a full database backup or performing copycluster using multiple storage locations, the task sometimes incorrectly failed with the error "Error in snapshot manifest file: Improperly ordered or duplicate storage ids." This issue has been resolved.

VER-49086

Backup/DR

A full backup config file generated by vbr in Vertica 8.0 contained an invalid entry, "None", for the objects attribute. This issue has been resolved.

VER-49217

Backup/DR

Previously the remove task sometimes failed when a node was DOWN. This issue has been resolved.

VER-49275

Backup/DR

Vertica backup and restore (vbr) now identifies which files it was unable to copy in the event of error backing up to a local destination.

VER-35560

Catalog Engine

DESERIALIZER warnings were written to the Vertica log when upgrading Vertica. The warnings were warranted, but were not a cause for concern. To prevent unnecessary concerns, the warnings are no longer written to the Vertica log unless you are using debug mode.

VER-48600

Catalog Engine

When merging projections, Vertica previously produced an internal error if an unsegmented projection existed on multiple, but not all, nodes. This issue has been resolved.

VER-48851, VER-39872, VER-42542

Catalog Engine

The ALTER table statement sometimes cleared sequences associated with identity columns, even when the identity column was not modified. This issue has been resolved.

VER-49142

Catalog Engine

Previously, Prejoin Projections caused GET_NODE_DEPENDENCIES() to return a permissions error. This issue has been resolved.

VER-48204

Client Drivers - ADO

VerticaDataReader.GetString() incorrectly rendered empty string values as NULL. This issue has been resolved.

VER-49041

Client Drivers - ADO

The Vertica ADO.net client driver created a new prepared statement on the Vertica server for every new query. This caused a prepared statement leak where a few statements on the client side mapped to many prepared statements on the server. This issue has been resolved.

VER-46120

Client Drivers - JDBC

Previously, Vertica would return an error when you used a LIMIT clause in a prepared statement subquery if your LIMIT clause included a question mark (?) placeholder rather than a number. This issue has been resolved.

VER-49286, VER-48531

DDL - Projection

A new algorithm was implemented in Vertica 8.0.1 for naming projections of tables that are created by CREATE TABLE... LIKE with the option INCLUDING PROJECTIONS. This algorithm avoids errors that were caused in earlier releases when a table was copied more than 99 times. For details, see the latest Vertica documentation:

https://my.vertica.com/docs/8.0.x/HTML/index.htm#Authoring/AdministratorsGuide/Projections/ProjectionNaming.htm.

VER-47502

DDL - Table

The issue where dropping a node caused the catalog to become corrupt has been resolved.

VER-48929

Data Collector

If Vertica updated a parameter that writes a Data Collector entry, while simultaneously attempting to write a Data Collector entry, a deadlock sometimes occurred. This issue has been resolved.

VER-48824

Data Removal - Delete, Purge, Partitioning

The PURGE_PARTITION function merged ROS containers across partition boundaries when the partition key did not match a key in the database. This issue has been resolved.

VER-25369

Client Drivers - VSQL Data load / COPY

COPY LOCAL always wrote exceptions and rejections files, which were empty if there were no exceptions or rejections. COPY LOCAL now only writes these files if there are exceptions or rejections.

VER-39991

Data load / COPY

Using the COPY parameters NO ESCAPE and DELIMITER together could produce an error (3280: ESCAPE AS and delimiter can not be the same value). This behavior has been corrected.

VER-47658

Database Designer Core

Previously, the Database Designer (DBD) did not consider automatic enforcement of enabled primary key or unique constraints when it created projections for a new table. Since auto enforcement requires special projections, you would subsequently need to refresh your primary key or unique constraint projections. The DBD now creates special projections for enabled key constraints when it creates projections for a table.

VER-44603, VER-46766

Admin Tools Database Designer Front-End/UI

Previously, when you ran the Database Designer from the Administration Tools, Vertica would create a backup of existing projections. Vertica no longer creates a backup of existing projections when you run Database Designer. Vertica removed the backup because:

  • Vertica did not use the backup, and, as a result, it was not needed.
  • In scenarios where there were a large number of existing projections, the backup could take too long, causing the operation to fail.
  • While running Database Designer from Admintools would prompt creation of the backup, running Database Designer through the Management Console would not.

Removing the feature from Admintools makes both processes consistent and identical. This issue has been resolved.

VER-50316

Documentation

Previously, dividing zero by zero returned zero. As of Release 8.0, Vertica returns, "ERROR 3117: division by zero".

VER-46658

Execution Engine

The file vertica.log would sometimes include the message, "Thread pool exited." Upon seeing the message, you might be concerned that there is a problem with your configuration. The message is internal and informational, is innocuous, and is related to the Vertica Execution Engine. This issue has been resolved. To help avoid confusion, this message no longer appears in the Vertica log file when the log file is set to the INFO level (the default).

VER-46819

Execution Engine

If you defined a primary or unique key constraint on more than 32 columns, Vertica incorrectly created many unnecessary key constraint projections. This issue has been resolved.

VER-47621

Execution Engine

Previously, using the ROUND or TRUNC function with a NUMERIC datatype would not always return a correct result. This issue has been resolved. Using ROUND or TRUNC with a NUMERIC datatype now consistently returns NUMERIC, retaining the original precision and scale.

VER-47826

Execution Engine

An INSERT... VALUES statement which specified column names using a different case from that used in the CREATE TABLE statement, could cause violation of enabled key constraints. This issue has been resolved.

VER-47923

Execution Engine

The PARTITIONS_ELIMINATED event type has been renamed to STORAGE_CONTAINERS_ELIMINATED.

VER-48214

Execution Engine

Previously, if your query included an early materialized merge join using Sidewise Information Processing (SIPs), the query could fail. In this scenario, the query would produce an internal error similar to the following: Internal EE Error (11) DETAIL: sip->maxKey HINT: Please report this error to Vertica; try restating your query This issue has been resolved.

VER-49122

Execution Engine

The issue where a user was dropped by a concurrent transaction while logging in causing Vertica to crash has been resolved.

VER-49740, VER-50227

Execution Engine

Due to a race condition, Vertica sometimes lost some rows during loading without producing an error message. This issue has been resolved.

VER-47117

Hadoop

Queries of ORC or Parquet data sometimes returned empty results incorrectly. This error occurred if the query used a WHERE clause with a Hive column type of CHAR. The workaround was to declare the column as VARCHAR instead. This workaround is no longer necessary.

VER-49014

Hadoop

When Vertica used external HDFS tables on many Hive partitions, Vertica could not query all the external HDFS table’s partitions, causing it to return in incorrect or incomplete results. This affected the WebHDFS and libhdfs++ connectors. This issue has been resolved.

VER-50266

Hadoop

Sentry authorization sometimes failed when Vertica read Parquet files from HDFS. This issue has been resolved

VER-49947

Kafka Integration

Vertica now uses an upgraded rdkafka library that fixes a potential deadlock issue when closing rdkafka handles.

VER-45536

Execution Engine Logging

In Vertica 7.2.1, if the client connection disconnected while a query was running, in some cases Vertica logged the same "Client has disconnected" error many times. This issue has been resolved.

VER-33391

Optimizer

Occasionally, the query optimizer chose two or more projections with different offsets (for example, 0 and 1) to execute a query, when it is not necessary to do so. This led to unnecessary resegmentation, which significantly increased execution time. This problem has been resolved.

VER-41072, VER-46541

Optimizer

LABEL hints can now be embedded in a CREATE TABLE's AS SELECT clause. For details, see https://my.vertica.com/docs/8.0.x/HTML/index.htm#Authoring/SQLReferenceManual/Statements/CREATETABLE.htm

VER-48039

Optimizer

When creating a transitive predicate, if one side of the predicate was an expression, Vertica did not correctly adjust the typmod of the field in the transitive predicate. This issue has been resolved.

VER-48602

Optimizer

If a query specified a LIMIT clause and called a subquery that specified its own Top-K limit, the outer query LIMIT was sometimes pushed down incorrectly into the subquery's Top-K limit and returned incorrect results. This issue has been resolved.

VER-48654

Execution Engine Optimizer

An issue with expression analysis for the REGEXP_REPLACE function sometimes caused incorrect query results if the data was in ROS. This issue has been resolved.

VER-48727

Optimizer

During INSERT, using a comma in a DIRECT hint for a non-existent table caused the node to fail. This issue has been resolved.

VER-48771

Optimizer

When configuration parameter ARCCommitPercentage was set to 0, Vertica.populated vertica.log with so many messages that the catalog directory's file system filled to 100 per cent and caused the node to fail. This problem was resolved by modifying messaging behavior related to this parameter.

VER-44920

Optimizer - Projection Chooser

Vertica was unable to direct certain queries to the appropriate live aggregate projection, and instead used the super projection. This issue has been resolved.

VER-48181

Optimizer - Statistics and Histogram

ANALYZE_STATISTICS returned no results for local temporary tables if their K-safety value was lower than the cluster's. This issue has been resolved.

VER-47982

Recovery

Sometimes a cluster would fail during the shutdown process with the following VAssert: "Unexpected startup state: SHUTDOWN". As a result, the database would not gracefully shutdown. This issue has been resolved.

VER-48247

Recovery

When there were no projections on a recovering node, Vertica still unnecessarily recovered empty tables and killed dirty transactions. This issue has been resolved.

VER-48252

Recovery

If a recovering table had no projections, Vertica continued to create sessions to recover the table and continuously sent spread messages. When Vertica exceeded the message limit, spread disconnected. This issue has been resolved.

VER-48562

Recovery

Table recovery took an excessive amount of time when there was nothing to recover in the database. With this fix, tables with nothing to recover will be marked as UP at the beginning of recovery. This issue has been resolved.

VER-39075

Catalog Engine ResourceManager

Previously, Vertica did not track memory allocated to catalog metadata. As a result, it could potentially over-allocate memory, causing out of memory errors. This issue has been resolved. If you have lowered your maximum memory setting or created a catalog resource pool as a workaround for this issue, you can now revert to default settings.

VER-47369

Security

The issue where a user with the pseudoesuperuser role could not see the entire contents of the PROFILES table has been resolved.

VER-48995

Security

In Vertica 7.2.3-7 and above, an LDAP connection leak occurred during authentication. This issue has been resolved.

VER-49499

Storage and Access Layer

The COMPACT_STORAGE meta-function created temporary directories in the Vertica data directory that Vertica did not clean up. This issue has been resolved.

VER-48167

Tuple Mover

After swapping partitions, if the Tuple Mover ran mergeout threads simultaneously, one thread sometimes used out-of-date mergeout cache information and failed to update the cache due to a race condition. This could cause node panic when the Tuple Mover attempted to execute the mergeout. This issue has been resolved.

VER-50009

Tuple Mover

If delete vector storage was dropped when the Tuple Mover performed a MOVEOUT operation, a segmentation fault could occur during validation checks. This issue has been resolved.

VER-44398

UI - Management Console

Previously, the MC installation script inadvertently checked for any port that included the numbers 5450 (for example,"54505"). If a port including the numbers 5450 was in use, MC installation failed. This issue has been resolved. During MC installation, Vertica now searches specifically for port 5450, which is needed for a successful MC installation.

VER-48406

UI - Management Console

After applying email settings in the Email Gateway page in Management Console (MC), MC did not provide the option to clear all fields. This issue has been resolved.

VER-48551

UI - Management Console

In Management Console, if you attempted to change the Node State Change threshold alert priority to Priority 1, it incorrectly re-set to Priority 2. This issue has been resolved.

VER-48688

UI - Management Console

A security issue during password validation in Management Console has been resolved.

VER-48925

UI - Management Console

In some cases, Management Console displayed an incorrect number of unsegmented projections. This issue has been resolved.

VER-49785

UI - Management Console

The Data Load Activity page in Management Console displayed an incorrect execution time for load jobs. This issue has been resolved.

VER-49016

WLA - Workload Analyzer

Vertica sometimes did not remove temporary files from the pgsql_tmp directory, which increased disk usage over time. This issue has been resolved.

Vertica 8.0.0-3: Resolved Issues

Release Date: 12/14/2016

This hotfix addresses the issues that appear below. Contact Vertica Technical Support to obtain this hotfix.

Issue

Component

Description

VER-50647 Client Drivers - JDBC When using JDBC, Vertica converted time zones incorrectly if the input value for dstSavings did not match that of the current calendar. This issue has been resolved.
VER-50319 Execution Engine Due to a race condition, Vertica sometimes lost some rows during loading without producing an error message. This issue has been resolved.
VER-50267 Hadoop Sentry authorization sometimes failed when Vertica read Parquet files from HDFS. This issue has been resolved.
VER-50178 Kafka Integration Vertica now uses an upgraded rdkafka library that fixes a potential deadlock issue when closing rdkafka handles.
VER-49781 Client Drivers - ADO The Vertica ADO.net client driver created a new prepared statement on the Vertica server for every new query. This caused a prepared statement leak where a few statements on the client side mapped to many prepared statements on the server. This issue has been resolved.
VER-49588 WLA - Workload Analyzer Vertica sometimes did not remove temporary files from the pgsql_tmp directory, which increased disk usage over time. This issue has been resolved.
VER-49118 UI - Management Console Enabling Extended Monitoring on Management Console can slow the performance of the Completed Queries Statistics chart on the Overview page over time. This issue has been resolved.

Vertica 8.0.0-2: Resolved Issues

Release Date: 10/12/2016

This hotfix addresses the issues that appear below. Contact Vertica Technical Support to obtain this hotfix.

Issue

Component

Description

VER-49133 Backup/DR A full backup config file generated by vbr in Vertica 8.0 contained an invalid entry, "None", for the objects attribute. This issue has been resolved.
VER-48837 Backup/DR When restoring a full database backup or performing copycluster using multiple storage locations, the task sometimes incorrectly failed with the error “Error in snapshot manifest file: Improperly ordered or duplicate storage ids.” This issue has been resolved.
VER-49085 Data Collector If Vertica updated a parameter that logged an entry in a Data Collector table, and another thread simultaneously attempted to flush the contents of that table, a deadlock could occur. This issue has been resolved.
VER-49347 Hadoop Using libhdfs++ to query encrypted ORC and Parquet files failed with an error. This issue has been resolved.
VER-49024 Hadoop When Vertica read ORC/Parquet files through HCatalog connector or ORC/Parquet readers with Hive partition columns in the table, if there were many distinct Hive partitions, this sometimes caused duplicate partition column values, which caused Vertica to return incorrect results. This affected the HCatalog connector and ORC and Parquet readers. This issue has been resolved.
VER-48869 Optimizer - Projection Chooser Vertica was unable to direct certain queries to the appropriate live aggregate projection, and instead used the super projection. This issue has been resolved.
VER-49021 Security In Vertica 7.2.3-7 and above, an LDAP connection leak occurred during authentication. This issue has been resolved.

Vertica 8.0.0-1: Resolved Issues

Release Date: 9/14/2016

This hotfix addresses the issues that appear below. Contact Vertica Technical Support to obtain this hotfix.

Issue

Component

Description

VER-48462 Build and Release, Client Drivers - Installation Package The Vertica 8.0 client package omitted the Javadoc for the Vertica JDBC-client. This hotfix re-adds the Javadoc.
VER-48616 Client Drivers - ADO

VerticaDataReader.GetString() incorrectly rendered empty string values as NULL. This issue has been resolved.

VER-48832 Recovery If a recovering table had no projections, Vertica continued to create sessions to recover the table and continuously sent spread messages. When Vertica exceeded the message limit, spread disconnected. This issue has been resolved.
VER-48768 Recovery When there were no projections on a recovering node, Vertica still unnecessarily recovered empty tables and killed dirty transactions. This issue has been resolved.
VER-48776 Documentation This fix updates the copyright year range in Vertica example files.
VER-48767 Tuple Mover After swapping partitions, if the Tuple Mover ran mergeout threads simultaneously, one thread sometimes used out-of-date mergeout cache information and failed to update the cache due to a race condition. This could cause node panic when the Tuple Mover attempted to execute the mergeout. This issue has been resolved.

Vertica 8.0.0: Resolved Issues

Release Date: 9/6/2016

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

Vertica 8.0.0: Resolved Issues

HPE has integrated hotfix 8.0.0-1 into Vertica downloads to address an issue in the initial Vertica 7.2.0 server downloads. This issue has been resolved and integrated into the current Vertica downloads. HPE strongly recommends the application of this update as soon as possible.

Issue

Component

Description

VER-45931 Admin Tools

In some virtual environments, Vertica was unable to collect statistical data for disk I/O using default settings. This affects Management Console, which cannot display the System Bottlenecks chart without disk I/O data.

This fix introduces the configuration parameter IOStatsIncludePattern, which is a PCRE regular expression pattern used to parse the /proc/diskstats system information file. This parameter is set to "^sd\\w+\\s*$" by default, to capture all block devices with an "sd" prefix.

Example to enable IOStatsIncludePattern:

select set_config_parameter('IOStatsIncludePattern', '^sda\\w+\\s*$');

-- capture only "sda" block devices

select set_config_parameter('IOStatsIncludePattern', '.*'); -- capture all block devices

VER-46142

AP-Geospatial

Queries using ST_Distance to perform POLYGON to POLYGON calculations sometimes returned inaccurate results. This issue has been resolved.

VER-46272

AP-Geospatial

In certain cases, ST_Intersects function returned incorrect results. This issue has been resolved.

VER-46909

AP-Geospatial

ST_Intersects incorrectly evaluated some GEOMETRY objects as too complex. This fix improves the evaluation process.

VER-37177

Backup/DR

Replacing an existing sequence with restore or replication dropped the grants for that sequence. This issue has been resolved.

VER-40308

Backup/DR

Vertica backups now include all dependent sequences for backed up objects. As a result, restores are now able to resolve any sequence conflicts that occur during the restore.

VER-40830

Backup/DR

The vbr backup script failed if it encountered a running rsync daemon without an rsync.configuration file. This issue has been resolved.

VER-46566

Backup/DR

Object level backups did not appear in the database_backups view. This issue has been resolved.

VER-46139

Backup/DR Basics

Attempting to restore a backup of a view created by another user sometimes caused the database to fail. This issue has been resolved.

VER-46520

Basics

After setting the parameter TerraceRoutingFactor, Vertica could fail if you issued the SHOW DATABASE statement after you subsequently upgraded the database. This issue has been resolved.

VER-44305

Catalog Engine

Vertica could fail if you dropped a user while Vertica was creating a local temp table in a different session for that same user. This issue has been resolved.

VER-45312, VER-45447

Catalog Engine

Vertica did not previously release the catalog memory for objects that were no longer visible by any current or subsequent transactions. The Vertica garbage collector algorithm has been improved.

VER-45594, VER-44881, VER-44430

Basics, Catalog Engine, Storage and Access Layer

New configuration variable MaxTieredPoolScale specifies the threshold for allocating chunks of memory from the system or dedicated pools for Vertica system components—-for example, for WOS containers. Above this threshold, Vertica allocates memory from the system (malloc), and returns it when no longer needed. Below this threshold, Vertica allocates memory from dedicated pools (talloc), which manage smaller memory allocations more efficiently.

VER-45855

Catalog Engine

In 7.2.2-1 and above, the MERGE_ALL_PROJECTIONS_WITH_SAME_BASENAME() function failed with an error on clusters with a k-safety of 0. This issue has been resolved.

VER-47564

Catalog Engine

After creating unsegmented projections in Vertica 7.1.x, then upgrading to 7.2.x, creating standby nodes generated an internal error. This issue has been resolved.

VER-46177

Client Drivers - ADO

In the Vertica ADO.net driver 7.2.2, inserting multiple commands into a single statement without parameters failed with an error. This issue has been resolved.

VER-46793

Client Drivers - ADO

When socket connections to Vertica servers closed unexpectedly, the ADO.NET driver still attempted to use the connection, causing queries to hang. This issue has been resolved.

VER-37968, VER-38975

Client Drivers - JDBC

The JDBC driver sometimes returned incorrect TIMESTAMPTZ values if the time zone specified in a query was different from the time zone on the Vertica server. This issue has been resolved.

VER-43935

Client Drivers - JDBC

The JDBC client library sometimes had poor performance when parsing a query with many string literals. The performance of such queries has been improved.

VER-45604

Client Drivers - JDBC

The JDBC connection property LoginTimeout did not work properly in Vertica releases 7.1 and 7.2. This issue has been resolved.

VER-31578

Client Drivers - ODBC

Previously, copy operations in progress were not always terminated when ODBC query executors were cleaned up; this resulted in "Unexpected message" errors in the server log and could result in prepared statements failing when autocommit is turned off. The problem has been corrected.

VER-44295

Client Drivers - ODBC

Previously, querying the V_CATALOG.ODBC_COLUMNS system table required an excessive amount of memory, which caused poor performance when querying the system table. This issue has been resolved.

VER-47246

Client Drivers - JDBC Client Drivers - VSQL

KV queries generated an error due to an incorrect permission restriction on a system table. This issue has been resolved.

VER-45973

DBD

Running multiple invocations of DESIGNER_DESIGN_PROJECTION_ENCODINGS in parallel sometimes generated an error. This issue has been resolved.

VER-44302

Catalog Engine DDL

Previously, Vertica took an exclusive global catalog lock while running a CREATE LOCAL TEMPORARY VIEW statement, which could slow performance. This issue has been resolved.

VER-47536

DDL - Projection

After rebalancing, CREATE TABLE LIKE INCLUDING PROJECTIONS queries on tables with unsegmented projections on all nodes would sometimes fail with an error. This issue has been resolved.

VER-48101

DDL - Projection

Running an UPDATE command on an empty table that contained an enabled primary or unique key constraint could cause a key projection to be generated before a superprojection had been created. A subsequent SELECT statement would then result in the error "Insufficient projections to answer query". This behavior has been corrected.

VER-45853

DDL - Table

When concatenating multiple table insertions with UNION or UNION ALL, and some values were set to NULL, Vertica sometimes incorrectly coerced other values to NULL constants. This issue has been resolved.

VER-45123

Data load / COPY

Some successful COPY commands incorrectly generated an error: "Unable to deparse query command type: 5". This issue has been resolved.

VER-46269

Data load / COPY

For apportioned loads from HDFS Connector, input_file_size and parse_complete_percentage in table load_streams contained incorrect values. This issue has been resolved.

VER-47731

Data load / COPY

Vertica did not clean up the empty rejected row files that COPY statements created. This issue has been resolved.

VER-47921

Data load / COPY

When the COPY statement was used with the S3 UDSource, paths containing globs could produce errors. Specifically, if every file in the glob expansion was empty, Vertica could return an error without loading the non-empty files. Vertica now loads the files containing data.

VER-44150

Database Designer Core

Previously, the Database Designer (DBD) did not consider automatic enforcement of enabled primary key or unique constraints when it created projections for a new table. Since auto enforcement requires special projections, you would subsequently need to refresh your primary key or unique constraint projections. This issue has been resolved. The DBD now creates special projections for enabled key constraints when it creates projections for a table.

VER-45512

Database Designer Core

Previously, loading UPDATE and DELETE queries containing subqueries into the Database Designer for optimization caused internal optimizer errors. This issue has been resolved.

VER-16396

Execution Engine

When using the SUM, SUM_FLOAT, or AVG function with a numeric data type, Vertica would silently overflow if the result exceeded the specified precision. By default, Vertica continues to permit silent numeric overflow. However, Vertica has added the ability to turn-off numeric overflow and add implicit precision to your numeric data types. See the Vertica documentation for more information.

VER-43164

Execution Engine

Enabling parallelism in DataTarget processing caused projections to lose rows and caused mismatched row counts for projections. Previously, the workaround for this issue was to disable DataTargetParallelism. This issue has been resolved.

VER-44480, VER-45688

Execution Engine

Due to insufficient locking on a Kerberos HDFS platform, use-after-free errors caused the cluster to fail if a background data-polling thread activated while a new vsql session was initializing. When this issue occurred, gblibc generated a corrupted double-linked list error in dbLog. This issue has been resolved.

VER-43209

FlexTable

Occasionally, when running the MATERIALIZE_FLEXTABLE_COLUMNS() function on a flex table with string columns, the node could fail. This issue has been resolved.

VER-45369

FlexTable

Querying flex table virtual columns under high concurrency failed with "ERROR: Length of a string in a return type must be greater than zero". This issue has been resolved.

VER-47628

FlexTable

In Vertica 7.2.3-2, copying timestamp values from Apache Avro to Vertica columns could cause the cluster to fail if the values were not written as Avro strings. With this fix, Vertica rejects the rows if the values are non-compliant. Only compliant Avro strings, such as "2016-03-14 11:06:09.287", are accepted.

VER-45140

Hadoop

Using HCatalog connector to load data from MapR generated an error because HCatUtil did not copy all the required JAR files. This issue has been resolved.

VER-45767

Hadoop

When reading a file from HDFS, Vertica uses a cached connection to the HDFS block location when possible. When a DataNode failed, Vertica sometimes still attempted to use the cached connection, causing the query to fail with an error. This issue has been resolved.

VER-45791

Hadoop

In Vertica 7.2.2, loading from the HDFS connector using HTTPS produced an error. This issue has been resolved.

VER-45971

Hadoop

In Vertica 7.2.2, the ORC Reader generated an error when it attempted to read empty ORC data files. This issue has been resolved.

VER-47052

Hadoop

In Vertica 7.2.2 and 7.2.3, the HCatalog connector could not query Hive tables in ORC or Parquet formats using MapR distributions. This issue has been resolved.

VER-47509

Hadoop

hcatUtil failed to copy jar files if the path name contained "test" or "source". This issue has been resolved.

VER-48137

Hadoop

When an exception occurred, the ORC (Optimized Row Columnar) parser did not correctly initialize the source, which could cause the parser incorrectly read a file multiple times. This issue has been resolved.

VER-45394

Kafka Integration

The vkconfig scheduler --add utility failed to recreate necessary missing tables for schemas that had been previously upgraded. This issue has been resolved.

VER-47634

License

In Vertica 7.2, AUDIT returned incorrect results for large tables with unsegmented projections. This could cause your license audit to overestimate your amount of data usage, and incorrectly show your usage as out of compliance. This issue has been resolved.

VER-44012

Execution Engine Optimizer

Previously, in scenarios where pattern matching would under-perform and a DFA algorithm would be better suited, pattern matching in Vertica performed sub-optimally. To resolve this issue, use the PatternMatchingUseDFAAlgorithm configuration parameter under Vertica Support guidance.

VER-43229

Optimizer

A cluster with fault groups of uneven sizes and with terrace routing enabled sometimes generated duplicate broadcasts for certain queries. As a result, the queries erroneously returned duplicate tuples. This issue has been resolved.

VER-45306

Optimizer

Running analyze_statistics with unsupported configuration parameter EnableAutoDMLStats enabled caused cluster to go down. This problem was resolved by permanently disabling the configuration parameter.

VER-45533

Client Drivers - JDBC Optimizer

The VerticaRouteableExecutor raised a Java exception while concurrently running the code in multiple threads. This issue has been resolved.

VER-45790

Execution Engine Optimizer

Analytic functions such as MEDIAN() that require sorted input occasionally returned inconsistent results. This occurred when input was derived from other functions that returned unsorted data. This issue has been resolved.

VER-46158

Optimizer

If you created a view over a query with aliased outputs, and the view also specified column names, Vertica sometimes returned the aliases instead of the view column names. This problem has been resolved.

VER-46366

Optimizer

In Vertica 7.2, certain queries with the LOWER function occasionally returned an error on exceeding output limits that were not reported in previous versions. This issue has been resolved.

VER-46494

Client Drivers - ODBC Optimizer

After upgrading to Vertica 7.2.1-3, using ANALYZE_CONSTRAINTS in a prepared statement generated an error. This issue has been resolved.

VER-46690

Optimizer

In Vertica 7.1, unoptimized plans for MERGE applied constant predicates to the source table before merging. This functionality was incorrect, and fixed in Vertica 7.2. With this fix, you can set the configuration parameter EnableMergePredPushDown at the database level to set MERGE to its previous 7.1 behavior. When you enable EnableMergePredPushDown, unoptimized MERGE pushes down predicates.

EnableMergePredPushDown is disabled (set to 0) by default. Set to 1 to enable.

Example to enable:

ALTER DATABASE database_name SET EnableMergePredPushDown = 1;

VER-47017

Optimizer

Using the URI_PERCENT_ENCODE function on text of certain lengths where all characters were encoded (such as foreign alphabets) caused the database to fail. This issue has been resolved.

VER-47489

Optimizer

COPY and INSERT performance could degrade substantially as the number of columns in a table increased. This issue has been resolved.

VER-47524

Optimizer Optimizer - Plan Stability

An initiator node would shut down upon evaluating a LAG function if the LAG function expression was not a constant. This issue has been resolved.

VER-45985

Optimizer - Statistics and Histogram

Running ANALYZE_STATISTICS on a table with no projections produced row counts for the entire database. This issue has been resolved.

VER-46251

Optimizer - Statistics and Histogram

Previously, ANALYZE_STATISTICS failed on binary data columns. This issue has been resolved.

VER-42355

Catalog Engine Performance tests

In Vertica 7.1 and 7.2, the performance of CREATE TABLE AS SELECT queries with unsegmented projections slowed. This issue has been resolved.

VER-36599

Refresh

When advancing the AHM, Vertica would sometimes produce the error, "ERROR 2150: AHM can't be set while retentive refresh is running," even when there was no retentive refresh running. This issue has been resolved.

VER-42642

Refresh

Tables with names containing some punctuation characters sometimes caused the REFRESH metafunction to fail. This behavior has been corrected.

VER-47343

Catalog Engine Refresh

Using the CANCEL_REFRESH function while there were queued refresh jobs caused node failure under some circumstances. This issue has been resolved.

VER-46902

ResourceManager

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

VER-46614

SDK

This fix resolves a serious issue related to dropping storage locations. If you retire a storage location, then drop it without first moving any files it contains, Vertica incorrectly rolls the Last Good Epoch (LGE) backward.

Be aware that storage locations you may have thought were empty may contain DFS files (due to installed UDxs, like Pulse, Place, or text search). The cluster subsequently becomes unsafe and you could lose data in a database failure or unsafe shutdown. With this fix, Vertica prevents you from deleting a storage location that still contains DFS files.

IMPORTANT: Before Shutting Down

If you suspect you might be in the situation described above, follow this workaround before shutting down your database.

To find out if your cluster is affected by this issue, check if your LGE is held back:

1. Run the following command. If the LGE is less than the Ancient History Mark (AHM), your LGE is held back:

=> SELECT AHM_EPOCH,LAST_GOOD_EPOCH FROM system;

2. If your LGE is held back, follow the steps below to drop your DFS files.

If your LGE is held back, you must drop your DFS files to fix this issue. Be aware that this can delete some of your data.

1. Run the following command to get directory names:

=> SELECT DISTINCT directory FROM dfs_storage;

2. Run the following command for each directory to delete it:

SELECT DFS_DELETE('/directory_name',true);

After you have dropped all DFS files, verify the LGE has advanced. If it has advanced, you can safely upgrade.

NOTE: Use caution whenever using DFS_DELETE. HPE recommends avoiding using this command when possible.

VER-43714

Security

LDAP Sync did not propagate user changes to Vertica if the LDAP server was configured to invalidate previous connections. This issue has been resolved.

VER-44664

Security

A confusing error message appeared when attempting to GRANT USAGE on a Resource Pool to a user. This issue has been resolved.

VER-44672

Security

Previously, after upgrading to Vertica 7.2.1, TRUNCATE TABLE privilege was not automatically granted to table owners. This issue has been resolved.

VER-45289

Logging Security

Data for dc_ldap_link_events was able to be queried only from one node. This issue has been resolved. You can now query this table from all nodes.

VER-46549

Security

Authentication sometimes failed due to a concurrency issue during LDAP setup, which caused the cluster to fail. This issue has been resolved.

VER-46859

Security

Deleting a group on the LDAP server, then running sync, sometimes caused Vertica to fail. This issue has been resolved.

VER-46426

Sessions

In Vertica 7.2.3 and above, segmentation fault occurred if single-line comments with a double hyphen (--) and no terminating new line caused Vertica to attempt to read non-existent memory. This issue has been resolved.

VER-46927

Sessions

An INSERT... VALUES statement which specified column names using a different case from that used in the CREATE TABLE statement, could cause violation of enabled key constraints. This issue has been resolved.

VER-48003

Sessions

If node names were more than 19 characters, it was possible for different sessions to have the same ID. This issue has been resolved.

VER-46718

Storage and Access Layer Tuple Mover

Vertica unnecessarily consumed blocks of memory that it did not free until database shutdown. With this fix, Vertica prevents this issue by using malloc and free to manage memory blocks larger than 128 MB.

VER-45584

Data load / COPY UDX

Using ORC and PARQUET files with UDSource is not supported. Attempting to do so generated a misleading error message. With this fix, a more accurate error message appears.

VER-30489

UI - Management Console

Management Console did not allow multiple OU filters when using LDAP. This issue has been resolved.

VER-38840

UI - Management Console

The Overview page in Management Console displayed a different number of Workload Analyzer recommendations than the Database Designer page. This issue has been resolved.

VER-45559, VER-46458

UI - Management Console

Uploading SSL certificates in Management Console (MC) would fail after upgrading from MC 7.2.x. This issue has been resolved.

VER-45849

UI - Management Console

Starting with CentOS/RHEL 7, network interfaces no longer follow the traditional eth[x] naming convention (for example: eth0, eth1). If your system does not use the traditional convention, Management Console could not display the System Bottlenecks chart. This issue has been resolved.

VER-48065

UI - Management Console

Previously, the MC installation script would inadvertently check for any port that included the numbers 5450 (for example, 54505). If a port including the numbers5450 was in use, MC installation would fail. This issue has been resolved. During MC installation, Vertica now searches specifically for port 5450, which is needed for a successful MC installation.
VER-48577 UI - Management Console

The User Sessions activity chart in Management Console did not initially display correctly. This issue has been resolved.

Known issues and limitations in Vertica 8.0.x

Updated: December 16, 2016

HPE 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 HPE Vertica implementations using HDFS storage locations.

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

Known Issues

Issue

Component

Description

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

New UDx names introduced in for Machine Learning in Vertica 8.0 can cause naming conflicts after installation. See the New Features Guide for details about changes in Machine Learning functionality, and the Machine Learning Functions section of the documentation for a full list of Vertica machine learning functions.

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 to Vertica 8.0, the Vertica 7.2.3 UDx's are not available for execution due to the naming conflict. Vertica 8.0 introduces the following functions:

• KMEANS

• LINEAR_REG

• LOGISTIC_REG

• BALANCE

• DELETE_MODEL

• SUMMARIZE_MODEL

• RENAME_MODEL

• NORMALIZE

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-48495 Data Removal - Delete, Purge, Partitioning, Vertica Log Text Search

It is not possible to move, swap, or copy partitions between tables that have text indices in non-default schemas.

Workaround: Redefine the tables' text indices in the public schema.

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-49641 Execution Engine

Exporting data from one Vertica database to another using the EXPORT TO VERTICA statement may or may not fail if the destination table includes an enabled primary key or unique constraint. Regardless of whether the statements fails, Vertica produces an error message similar to the following: ERROR 2611: Client Server protocol error. Message type 'ServerInfo' is invalid in state 'CommandDone' Note: This issue does not occur for enabled check constraints.

Workaround: Disable primary key and unique constraints on the destination table before you export. Manually validate table constraints after export using the ANALYZE_CONSTRAINTS meta-function. Resolve constraint violations (for example, duplicate keys), and then re-enable your constraints.

For additional information and syntax for the meta-function, refer to:

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.

Workaround:

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.

VER-50024 UI - Management Console When loading an S3 job in Management Console, the Failed Load Details dialog may not load correctly in the following scenario: The Copy Parameter field was empty The AWS region field was filled incorrectly A vsql user did not set credentials correctly before viewing the job on MC

 


Legal Notices

Warranty

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 - 2016 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 HP