Release Notes

Vertica

Software Version: 7.0.x

 

Updated: April 17, 2017

 

About Vertica Release Notes

Security Warnings

Vertica 7.0.2-13: Resolved Issues

Vertica 7.0.2-12: Resolved Issues

Vertica 7.0.2-11: Resolved Issues

Vertica7.0.2-10: Resolved Issues

Vertica 7.0.2-9: Resolved Issues

Vertica 7.0.2-8: Resolved Issues

Vertica 7.0.2-7: Resolved Issues

Vertica 7.0.2-6: Resolved Issues

Vertica 7.0.2-5: Resolved Issues

Vertica 7.0.2-4: Resolved Issues

Vertica 7.0.2-3: Resolved Issues

Vertica 7.0.2-2: Resolved Issues

Vertica 7.0.2-1: Resolved Issues

Vertica 7.0 SP1: New Features and Resolved Issues

Vertica 7.0.0-1: Resolved Issues

Vertica 7.0.0: New Features and Resolves Issues

Vertica 7.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 7.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:

Downloading Hotfixes

Unless otherwise indicated, hotfixes are made available via the customer FTP site. Hotfixes are available to Premium Edition customers only.

To download a hotfix, Premium Edition customers can enter a support case at their my.vertica portal. The Vertica technical support team will ensure you have the correct credentials prior to downloading the hotfix.

On rare occasions, Vertica replaces the software on the my.vertica.com/downloads site with a particular hotfix. Refer to these Release Notes to learn where you can access a particular hotfix.

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 7.0.2-13. Vertica strongly recommends you upgrade to this version as soon as possible.

Vertica 7.0.2-13: Resolved Issues

Release Date: 4/17/2017

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

This hotfix addresses the issue below.

Issue

Component

Description

VER-53669

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 7.0.2-12: Resolved Issues

Release Date: 3/01/2016

This hotfix addresses the issue that appears below. Contact Vertica Technical Support to obtain this hotfix.

Issue

Component

Description

VER-43739 Execution Engine, Optimizer Using IN lists with constant NUMERIC expressions (such as date_part) within CREATE TABLE AS SELECT sometimes caused core dump under certain circumstances. This issue has been resolved.

Vertica 7.0.2-11: Resolved Issues

Release Date: 12/2/2015

This hotfix addresses the issue that appears below. Contact Vertica Technical Support to obtain this hotfix.

Issue

Component

Description

VER-42173 Client Drivers - JDBC The unused date portion of a java.sql.Time object returned by the driver during ResultSet.getTime (int, Calendar) was sometimes incorrect, This occurred in situations when the application requested the driver to convert the time into a timezone different than the JVM timezone.
VER-40024 Optimizer If a meta-function was incorrectly used in a query with a set operator, it was not rejected, causing the cluster to fail. This issue has been resolved.
VER-42480 Recovery Vertica would sometimes perform an incremental recovery rather than a recovery by container for a node performing a complete recovery. This issue has been resolved.

Vertica 7.0.2-10: Resolved Issues

Release Date: 6/30/2015

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

Issue

Component

Description

VER-39402 Execution Engine Internal tables incorrectly handled certain combinations of permissions and objects, which in rare scenarios caused node failure. This issue has been resolved.
VER-39337 Optimizer - Statistics and Histogram Previously, running IMPORT_STATISTICS and EXPORT_STATISTICS functions could fail when tables contained user defined data types. With this hotfix, these functions ignore columns with user defined data types.
VER-39106 SDK When vt_creatFuncObject instantiated a UDL object, a destructor for the object was not always called. This issue has been resolved. After you implement this upgrade, remove workarounds in UDx code that explicitly invoke object destructors.

Vertica 7.0.2-9: Resolved Issues

Release Date: 6/10/2015

This hotfix addresses the issue that appears below. Contact Vertica Technical Support to obtain this hotfix.

Issue

Component

Description

VER-38704 Communications/messaging, Execution Engine A race condition occasionally caused the UNION operator to hang before the query finished executing. This issue is resolved.

Vertica 7.0.2-8: Resolved Issues

Release Date: 6/1/2015

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

Issue

Component

Description

VER-38008 Basics Concurrent ALTER PROJECTION and DROP TABLE CASCADE statements sometimes caused nodes to panic. This issue has been resolved.
VER-38002 Catalog Engine The epoch management process sometimes caused very long exclusive locks. With this hotfix, the lock time is reduced.
VER-38085 Execution Engine, Optimizer Memory usage during ANALYZE STATISTICS was sometimes excessive, causing nodes to fail. With this hotfix, memory usage has been substantially reduced during this operation.
VER-38308 Execution Engine Overflows in internal calculations with numeric fields could result in the next column being partially overwritten. This could lead to incorrect results and, in rare circumstances, cluster failure. This fix implements a stop-gap solution which detects and aborts the affected query to prevent cluster failure and incorrect results.
VER-38714 Execution Engine When nodes joined or left the cluster during the execution of a DDL operation, the DDL sometimes rolled back with the error "A node has entered/left the database cluster." This issue has been resolved.
VER-38986 Front end - Parse & Analyze When outer queries referenced subqueries with constant columns and aggregation, outer query predicates that included those constant columns sometimes were applied incorrectly to the subqueries' aggregations. This issue has been resolved.

VER-38728

Optimizer Queries with SET operations using constant columns sometimes failed with core dumps, causing Vertica nodes to fail. This issue has been resolved.

VER-38836

Optimizer In certain cases, NOT NULL constraints were not respected when subqueries were used to update a table. This issue has been resolved.
VER-38469 Security LDAP parameters with special characters were sometimes incorrectly parsed, causing the server to fail. This issue has been resolved.
VER-38062 Storage and Access Layer Vertica periodically performs various checks on the system for performance and usage. Previously, in certain cases, the check would divide by 0, causing an error. The issue has been resolved.

Vertica 7.0.2-7: Resolved Issues

Release Date: 2/24/2015

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

Issue

Component

Description

VER-36016

Data load / COPY

In certain situations, queries that perform merge joins did not return correct results. This issue has been resolved.
VER-35949 Monitoring If users made changes to Data Collector policies in Vertica versions 7.0.1 through 7.1, any policy settings existing prior to those changes were lost when nodes were restarted. This issue has been resolved.
VER-36688 Optimizer When Vertica performed a hash join using a dual projection as the outer join input, the query sometimes failed due to insufficient memory for the inner join input. This issue has been resolved. Additionally, this fix may improve the performance of existing queries where dual projections were previously used as the outer join input.
VER-36706 Transactions In some instances, a DROP_PARTITION operation did not successfully cancel a conflicting MERGEOUT operation, and the DROP_PARTITION timed out waiting for a table lock. Additionally, incorrect TIMEOUT error messages sometimes occurred when the server was actually successful in canceling the MERGEOUT operation. This issue has been resolved.

VER-36915

Optimizer

In databases of more than 4 billion rows in a table, ANALYZE_HISTOGRAM sometimes updated columns with no statistics. This issue has been resolved.

Vertica 7.0.2-6: Resolved Issues

Release Date: 01/15/2015

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

Issue

Component

Description

VER-34369

Backup/DR

Preparing Vertica nodes for backup took longer in proportion to the number of nodes in the cluster. This has been resolved by preparing nodes for backup in parallel.

VER-35929

Data load / COPY

Bulk loading data using the COPY command sometimes resulted in sequence exceeded max value error. This issue has been resolved.
VER-36058 Execution Engine Some queries using a LIMIT clause sometimes incorrectly produced 0 rows of results. This issue has been resolved.

Vertica 7.0.2-5: Resolved Issues

Release Date: 11/18/2014

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

Issue

Component

Description

VER-35235

Basics

TO_DATE and TO_TIMESTAMP were returning incorrect results when Sunday was used in the query. This issue has been resolved.

VER-35625

Client Drivers - JDBC

Previously, the HDFS UDSource could not be used from a JDBC client when HDFS and Vertica were both configured to authenticate with kerberos because JDBC did not request forwardable kerberos tickets. The issue has been fixed.

VER-35133

Data load / COPY

If a user has run ALTER COLUMN SET DATA TYPE to change the column width of a string column, and applied one of four encoding types (BLOCK_DICT, COMMONDELTA_COMP, DELTARANGE_COMP, or NONE) to the column, running queries on the column sometimes caused the database to fail or caused incorrect strings to be returned. This issue has been resolved.

VER-34835

Database Designer Core

Nodes sometimes failed if you dropped a database design before Database Designer finished executing. This issue has been resolved.

VER-35198

Execution Engine

When the DELTARANGE_COMP or COMMONDELTA_COMP compression type were applied to float columns, sometimes reading from those columns returned incorrect results. This issue has been resolved.

VER-35276

SDK-R

When the close argument was issued, a User Defined Extension (UDx) in R created defunct Vertica-R processes that were not cleaned up immediately. This issue has been resolved.

VER-35405

SDK-R

The vertica-udx-R binary previously depended on liblzma. This dependency has been removed.

VER-35417

Security

OpenSSL/TLS (client and server) has been upgraded to version 0.9.8zc

VER-35523

Tuple Mover

The MOVE_PARTITIONS_TO_TABLE and SWAP_PARTITIONS_BETWEEN_TABLES functions previously performed a moveout operation on all the data in the WOS, which sometimes caused errors in busy databases. This issue has been resolved.
 

Vertica 7.0.2-4: Resolved Issues

Release Date: 10/8/2014

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

Hotfix 7.0.2-3 introduced a minor SDK incompatibility, which is fixed in hotfix 7.0.2-4. This does not affect users upgrading from 7.0.2-2 or below to 7.0.2-4. Users upgrading from 7.0.2-3 must recompile their SDK based functions (Udx).

Issues VER-33119, VER-34573, and VER-34638 were originally addressed in hotfix 7.0.2-3. These fixes are now included in 7.0.2-4.

Issue

Component

Description

VER-34640

Client Drivers - JDBC

A deadlock in the JDBC driver could occur when the Close() methods of a Connection and a child PreparedStatement were called concurrently. The issue has been fixed.

VER-33063

Execution Engine

Running the COUNT(DISTINCT) function negatively affected the performance of the APPROXIMATE_COUNT_DISTINCT function. This issue has been resolved.
VER-33119 Execution Engine Previously, the Vertica server sometimes failed when handling error conditions that occurred when deleting queries being terminated due to external causes, such as insufficient resources or user interrupt. The server now logs the error condition and continues to terminate the query.
VER-34573 Execution Engine Functions called on a TIMESTAMP that was truncated to a date sometimes caused Vertica to fail when the input for TIMESTAMP was NULL. This issue has been resolved.
VER-34638 Execution Engine Joins with a large sorted inner relation and a sorted outer relation occasionally failed in SIPS. This issue has been resolved.

VER-34165

Hadoop

When retrieving data from an HDFS cluster with Kerberos enabled, the HDFS connector failed with an error, or returned fewer rows than expected. This issue has been resolved.

VER-34923

Transactions

A DROP_PARTITION operation is expected to interrupt or cancel a conflicting MERGEOUT operation. In some instances the MEREOUT operation does not cancel and the DROP_PARTITION times out waiting for a table lock. Furthermore, a race condition in error reporting can sometimes result in a CANCEL error message being returned instead of the expected LOCK TIMEOUT error message.

Vertica 7.0.2-3

Release Date: 9/23/2014

We have removed hotfix 7.0.2-3 for further testing. We will post the hotfix and release notes for 7.0.2-4 as soon as it is available.

Vertica 7.0.2-2: Resolved Issues

Release Date: 8/27/2014

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

Issue

Component

Description

VER-32891

Admin Tools Catalog Engine

(Spread) Stopping spread on a single node in a cluster of 20 or more nodes that use direct point-to-point communication caused the database to exit all nodes in the cluster. This issue has been resolved.

VER-32882

Client Drivers - ODBC

The SQLGetData() call incorrectly returned SQL_SUCCESS when the buffer length argument was equal to zero. This issue has been resolved.

VER-34157

Communications/ messaging

An internal error was being mistakenly reported in some rebalance operations. The error in the Vertica log contained the following text:

<INTERNAL> ... 5445: VIAssert(_currentMessage.buf.avail() >= _currentMessage.getBufferDataSize()) failed

This issue has been resolved.

VER-34446

Execution Engine

Queries calculating the total number of results in a timestamptz column returned inconsistent results. This issue has been resolved.

VER-33955

Execution Engine

When processing a query that is terminated, the database would sometimes fail during the error recovery process. This issue has been resolved.

VER-34286

Execution Engine

Vertica incurred additional overhead planning loads on tables with numerous storage containers. This issue has been resolved.

VER-34305

Optimizer

String NULLs in statistics histograms were previously not treated as NULL, leading to incorrect value ranges. This issue has been resolved.

VER-34210 Recovery After a manual system recovery was unsuccessful, the node was restarted in order to re-join the cluster. Then after the node was restarted, the buddy projections had differing numbers of total rows. This issue has been resolved.

Vertica 7.0.2-1: Resolved Issues

Release Date: 8/12/2014

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

Issue

Component

Description

VER-31400

AP-Geospatial

Indexing large data sets sometimes failed in Vertica Place. This issue has been resolved.

VER-32420

Admin Tools

Vertica AdminTools sometimes refused to start the database if any host was unavailable. This issue has been resolved.

VER-31225

Backup/DR

When copying a database between Vertica 7.x clusters using the vbr.py utility, the spread configuration was overwritten, sometimes leaving the target database unusable. This issue has been resolved.

VER-31267, VER-31608

Catalog Engine Backup/DR

Canceling a vbr.py backup with Ctrl+C did not always close the session. This problem has been resolved. Interrupting a backup with Ctrl+C now closes the session immediately. Uninterrupted incremental backups may run faster.

VER-33865

Client Drivers- ADO

The ADO.net installer was versioned incorrectly, causing a problem with uninstall and upgrade. This issue has been resolved.

VER-32544

Backup/DR

In some cases object-level restore removed files of unrelated, not-yet committed transaction. The affected transaction, unaware, could commit. This resulted in the following error when a query or other operation later tried to read from those files.
FileColumnReader: unable to open position index /data/v_node0001/005/45035996744778005/45035996744778005_0.pidx: No such file or directory

VER-31829

Catalog Engine

The ANALYZE_STATISTICS function incorrectly issued a commit. This issue has been resolved.

VER-32014

Catalog Engine

Certain DDL (e.g., REPLACE LIBRARY) could result in catalog memory leaks, or in rare cases crash the database. This issue has been resolved.

VER-32671

Catalog Engine

When using an ALTER statement with multi-byte characters (such as Japanese characters) the database sometimes failed. This issue has been resolved.

VER-32987, VER-32988

Client Drivers - ODBC Client Drivers - VSQL

The Vertica ODBC client driver and vsql have updated to the OpenSSL library version 0.9.8za.

VER-33372

Catalog Engine Communications/ messaging

When a competing lock request timed out, the attempted lock was sometimes unable to be fully released, which could eventually cause the node to fail. This issue has been resolved.

VER-34159

Communications/ messaging

An error in calculation sometimes caused some rebalance operations to fail. This calculation has been corrected.

VER-30124

DDL

Running ANALYZE_CONSTRAINTS on wide tables, including tables with 0 rows, sometimes exceeded available memory. This issue has been resolved.

VER-31472

Data load / COPY

When COPY had a filter and cooperative parsing was disabled, COPY could sometimes silently skip the last several rows in a file. This issue has been resolved.

VER-31926

Data load / COPY

With this fix, ephemeral nodes are now included when user queries reference external tables.

VER-33922

Data load/ COPY

When selecting directly from an external table, load parallelism was sometimes significantly reduced. This issue has been resolved.

VER-33704, VER-33953

Database Designer Core

Nodes sometimes failed when a database design was dropped before the Database Designer finished executing.

VER-31016

Execution Engine

Certain queries involving GROUP BY where the data was partially sorted could result in a server crash. This issue has been resolved.

VER-31454

Execution Engine

Queries that used ranges with integer bounds, and that were sorted by date/time, sometimes caused the database to fail with an internal optimizer error. This issue has been resolved.

VER-31839

Execution Engine

When the catalog was modified while an EXPORT_STATISTICS call was running, the database server sometimes failed.. This issue has been resolved.

VER-31395

Front end - Parse & Analyze

Invalid date errors did not appear when an UPDATE statement included the DATE function. This issue has been resolved.

VER-30692

Optimizer

When the COALESE function was used on multiple consecutive full outer joins, the query failed. This issue has been resolved.

VER-30973

Optimizer

Inconsistent results sometimes occurred with spilled joins. The inconsistencies occurred when the outer join input was sorted with a different column sequence ordering from the join key columns. This issue has been resolved.

VER-31082

Optimizer

UNION ALL queries using a GROUP BY clause did not group data in individual SELECT statements. This release resolves this issue for queries that do not include aggregate functions.

VER-31144

Optimizer

A new global configuration parameter named "ExcludeEphemeralNodesInQueries" is available. Setting this parameter excludes all non-initiator EPHEMERAL nodes from SELECT plans. By default this feature is disabled.

VER-31119, VER-31829

Optimizer

The ANALYZE_CONSTRAINTS function incorrectly issued a commit. This issue has been resolved.

VER-31602, VER-31455

Optimizer

An OVER() clause that specified two or more PARTITION BY columns could sometimes produce incorrect results. This occurred when the analytic function was run on a multi-node system, and an order was needed that was compatible with the PARTITION BY order, but did not match it exactly. This issue has been resolved.

VER-31667

Optimizer

When ANALYZE_CONSTRAINTS() is used on constraints of less than or equal to 20 columns, any violating column values are displayed. For constraints of more than 20 columns, ANALYZE_CONSTRAINTS() now provides a query, that when run, returns the violating column values. This minimizes resource usage.

VER-31925

Optimizer

When the catalog was modified while an EXPORT_STATISTICS call was running, it sometimes caused the database server to fail. This issue has been resolved.

VER-32073

Optimizer

When a query ran for an extended period, it ran out of memory and failed to retry due to a DDL statement interfering with the query replan. This problem has been resolved.

VER-32655

Optimizer

In large catalogs, AnalyzeRowCount was consuming large amounts of memory and causing database failures. This issue has been resolved.

VER-32746

Optimizer

Queries with equality predicates on tables with segmented projections did not return rows on non-default locales. This issue has been resolved.

VER-32765

Optimizer

Query estimation was incorrect when there was a union on top of views or on top of a n-level subquery (where n>= 2)

VER-32887

Optimizer

Queries with "WHERE false" or equivalent clauses scanned tables referenced in subqueries even though no results were returned by the query. This issue has been resolved

VER-31763

Query Generator

Collecting statistics on large columns with mostly NULL values sometimes produces the incorrect conclusion that the entire column is NULL, ignoring min or max estimates. This issue has been resolved.

VER-30658

SDK

Previously, if a COPY statement called a User Defined Extension (UDx) to obtain the value for a column, a file handle could be left open when the UDx exited. This could eventually cause the database node to run out of open file handles. This issue has been resolved.

VER-31580

SDK-Java

Previously, SizedColumnTypes.getColumnName(index INT) returned NULL when called inside the setup method of a UDx (user-defined extension). With this fix, it now returns the column name.

VER-33345

SDK-Java

PartitionWriter.setNumericNull sometimes incorrectly produced a negative value rather than null output. This issue has been resolved.

VER-32986

Security

The Vertica server has updated to the OpenSSL library version 0.9.8za.

VER-31724

Storage and Access Layer

With this fix, you can now use the ADD_LOCATION() function to add a read-only directory for USER data. Additionally, an unavailable USER location will no longer prevent a node from starting up.

VER-31896

UI-Management Console

Due to a Jetty issue that caused mishandled URLs, the Database Designer wizard in Management Console sometimes failed with HTTP Error 400. This issue has been resolved.

VER-31952

UI-Management Console

Uploading a query file to Database Designer in Management Console sometimes failed in multi-node systems that included an inaccessible IP. This issue has been resolved.

VER-32776

UI-Management Console

Previously, the workload operation was not performing its daily run. The issue has been resolved.

VER-32904

UI-Management Console

Previously, Management Console on remote non-database nodes imported through the public network. All private IPs showed the database and node state as unknown, but displayed all other details normally. The issue has been resolved.

Vertica 7.0 SP1: New Features and Resolved Issues

Release Date: 3/3/2014

What’s New in Vertica 7.0 SP1

The list below describes some of the new features introduced in Vertica 7.0.1. To see a complete list of additions and changes introduced in this release, refer to the Vertica 7.0.x New Features Guide.

Vertica 7.0 SP1: Resolved Issues

Issue

Component

Description

VER-29818

Backup/DR

Schema level backups fail if a temporary table exists at the checkpoint epoch of the super projection. This issue has been resolved.

VER-30388

Admin Tools

Resolved an installer issue that occurred when the loopback IP address was not 127.0.0.1 (e.g. 127.0.1.1, as found on some versions of Ubuntu).

VER-30413

Admin Tools

When monitoring clusters with a large number of nodes, admin tools database monitoring could incorrectly display nodes as DOWN. This issue has been resolved.

VER-30362

Client Drivers - JDBC

A potential security vulnerability related to the connection load balancing mechanism has been resolved.

VER-30309

Client Drivers - ODBC

In previous releases, ODBC queries with more than 3000 parameters failed with a lost synchronization with server error. This issue has been resolved.

VER-30022

DDL

When an ephemeral node was down, the analyze_statistics command failed, and returned the insufficient projections to answer query error. This issue has been resolved.

VER-30442

DDL

In previous releases, if you did not pass arguments to APPROXIMATE_COUNT_DISTINCT_SYNOPSIS, the database failed with a PANIC error and the cluster went down. This issue has been resolved.

VER-30443

Data load / COPY

The EXPORT TO VERTICA / COPY FROM VERTICA statements in Vertica 7.0.0 could prevent copying data from some external clusters, especially Vertica 6.x clusters. This issue has been resolved.

VER-30853

Data load / COPY

You can use the REJECTED DATA AS <table> clause and the REJECTMAX parameter when loading data. However, if the number of load rejections exceeded the REJECTMAX limit, the table was not created. This issue has been resolved.

VER-30184

Database Designer Core

While using admin tools, the Database Designer failed to run in Incremental Mode. This problem has been resolved.

VER-30743

Database Designer Core

The Database Designer intermittently failed to deploy successfully and aborted with the error message: Subquery used as an expression returned more than one row. This issue has been resolved.

VER-30414, VER-30937

Execution Engine

Queries using ranges with integer bounds, and sorted by date and time, could cause the database to fail with an internal optimizer error. This issue has been resolved.

VER-30591

Execution Engine

Running EXPLAIN on a COPY FROM VERTICA statement could result in an internal error. This issue has been resolved.

VER-30746

Execution Engine

In cases where NULL values were frequently used and sorted non-RLE column(s) were used in predicates, Vertica could return incorrect query results. This issue has been resolved.

VER-30632

Installation Program

In release 7.0.0, the installer could search for the broadcast address on the wrong interface and cause an error that halted installation. This issue could occur when a host was specified in the hosts parameter with different IP addresses. In release 7.0.1, this issue is resolved and the installer validates that each specified host is identified with a single IP address. The installer also identifies the correct broadcast address for all IP address(es).

VER-29404

Optimizer

When queries had joins on columns with a high data skew, and the columns were used in other joins, query performance was slow because the joins spilled to disk. This issue has been resolved.

VER-29798

Optimizer

In previous releases, when Vertica performed a sorting operation as a result of a DISTINCT or GROUP BY clause, certain data types (INTEGER, DATE/TIME, NULL) could not be implicitly cast as VARCHAR data. This issue has been resolved.

VER-29969

Optimizer

Inconsistent query results resulted when obtained when an ORDER BY clause was used in a sub-query. This issue has been resolved.

VER-30451

Optimizer

Using an ORDER BY clause on a UNION ALL in a sub-query generated a MERGE ALL that contained the wrong merge keys. This issue has been resolved.

VER-30471

Optimizer In previous releases, APPROXIMATE_COUNT_DISTINCT included NULL values in the results. This issue has been resolved and the function now excludes NULL values from its count.

VER-30118

Performance tests Vertica sometimes underestimated planning resources for queries with LONG VARCHAR or LONG VARBINARY in clusters with many nodes, which sometimes resulted in swapping. This issue has been resolved.

VER-29233

Admin Tools System:Performance System:Stability If you accidentally started two Vertica processes as the same node, the cluster could sometimes fail. This issue has been resolved.

VER-26775

Tuple Mover After deleting all rows from a table, mergeout and moveout activities could continue until the vertica.log file consumed all available disk space. The Vertica database shut down when it could no longer write to the catalog. This issue has been resolved.

VER-24561, VER-30180, VER-30532

Tuple Mover, Rebalance, Recovery Refresh Rebalance sometimes ran out of memory when run on a large cluster with many storage containers. This issue has been resolved.

VER-23305

UI - Management Console From Management Console, you could not connect to a database if the database password contained a pound sign (#) character. This issue has been resolved.

Vertica 7.0.0-1: Resolved Issues

Release Date: 12/20/2013

This hotfix addresses the issue that appears below. Contact Vertica Technical Support to obtain this hotfix.

Issue

Component

Description

VER-30362

Server

This update resolves security vulnerability in the Vertica server. HP strongly recommends the application of this update as soon as possible.

Vertica 7.0.0: New Features and Resolved Issues

Release Date: 12/10/2013

What’s New in Vertica 7.0.0

The list below describes some of the new features introduced in Vertica 7.0.0. To see a complete list of additions and changes introduced in this release, refer to the Vertica 7.0.x New Features Guide.

Upgrade Considerations

Installer changes

The Version 7.0.0 installer introduces new platform verification tests that prevent the install from continuing if the platform requirements are not met by your system. Manually verify that your system meets the requirements in Before You Install Vertica section of the Vertica Installation Guide before you update the server package on your systems. These tests ensure that your platform meets the hardware and software requirements for Vertica. Previous versions documented these requirements, but the installer did not verify all of the settings. Version 7.0.0 introduces the new installation parameter --failure-threshold that allows you to change the level at which the installer stops the installation process based on the severity of the failed test. By default, the installer stops on all warnings. You can change the failure threshold to FAIL to bypass all warnings and only stop on failures. However, your platform is unsupported until you correct all warnings generated by the installer. By changing the failure threshold you are able to immediately upgrade and bring up your Vertica database, but performance cannot be guaranteed until you correct the warnings.

LDAP Authentication Changes

If you have LDAP enabled over SSL/TLS, in Vertica 7.0, the certificate authentication is more secure than in Vertica 6.1. Before you upgrade to Vertica 7.0, there are several tasks that you need to perform so that you can connect to the LDAP server after the upgrade. You can also choose to revert to the more permissive behavior used in Vertica 6.1. See the Vertica 7.0.x Installation Guide for information on preparing for the new authentication, or reverting to the old behavior.

MC Documentation Error

The Vertica 7.0.x Installation Guide incorrectly states that Management Console requires a separate node. In Vertica 6.1.3 and later, Management Console can be installed on any node in the cluster.

Vertica 7.0.0: Resolved Issues

Issue

Component

Description

VER-27783

Admin Tools

The admintools -t rebalance_data tool was not working properly for rebalance operations that did not change the cluster's K-safety. This issue has been resolved. You can optionally call the SELECT REBALANCE_CLUSTER() function.

VER-25085

Backup/DR

In previous releases, the VBR utility rsync deamons ran as the root user and group. As of Version 7.0, the rsync deamons run as the dbadmin user and group.

VER-26900

Backup/DR

In previous releases, restoring an object-level hard-linked local backup failed if the catalog directory existed on a separate Linux file system. This has been resolved. If VBR detects that the catalog is on a separate Linux file system, it copies the file, rather than linking to it.

VER-28154

Backup/DR

Before Version 6.1, any missing data files detected during startup after cloning a database were logged in a descriptive message. However, these were not logged in 6.1. This issue has been resolved. In Vertica 7, the files are once again logged.

VER-26001

Basics

The PatternMatchAllocator configuration parameter is disabled by default to prevent rare node failures.

VER-25669

Catalog Engine

Due to a change in how transaction catalog storage works in Vertica 6.0 and later, the amount of space that the transaction catalog takes up can increase significantly during and after the upgrade from version 5.x to 7.0.0. To determine the amount of space the catalog folder is using, run 'du -h' on the catalog folder. For example: [dbadmin@localhost ~]$ du -h /home/dbadmin/db/v_db_node0001_catalog/Catalog If you determine you need more space, turn on CompressCatalogOnDisk. (See the General Parameters section of the Vertica 7.0.x Administration Guide for more information.)

VER-25906

Catalog Engine

Queries on system tables that described constraints did not return correct results when they used the = operator or 'like" to find a specific string without specifying a wild card. This issue has been resolved.

VER-27065

Catalog Engine

Running GET_NODE_DEPENDENCIES() on temporary tables that have pinned projections caused the database to fail. This issue has been resolved.

VER-25592

Client Drivers - ADO

In previous releases, a race condition in ADO.net was caused by open two connections to Vertica server simultaneously. Now the connection open operation is thread-safe.

VER-27182

Client Drivers - ADO

The Vertica ADO.net driver incorrectly converted double values for some locales. This issue has been resolved.

VER-25308

Client Drivers - JDBC

Customers sometimes got an out-of-memory error when using JDBC batch insert in previous releases. In Version 7, customers can turn on streaming batch insert to avoid this issue.

VER-25409

Client Drivers - JDBC

When constructing a timestamp by passing a Calendar object to ResultSet.getTimestamp(int, Calendar), the driver produced an incorrect result if the time did not exist in the JVM's default time zone. The issue has been resolved.

VER-25487

Client Drivers - JDBC

When performing a batch insert operation with AUTOCOMMIT disabled, any batches after the first batch were erroneously marked as successful, even if some records were rejected by the server. The issue has been resolved.

VER-25898

Client Drivers - JDBC

Previously, the JDBC driver returned an incorrect SQLState when data errors caused a non-batched prepared insert operation to fail. The issue was resolved, and now it returns class 22 SQLStates. In Java 6 and newer JVM's, the exception thrown is a SQLDataException instead of a SQLException, to more accurately categorize the error. Batched insert operations continue to throw BatchUpdateException if there are failures due to data errors.

VER-27303

Tool Integration Client Drivers - JDBC

Prior to this release, the V_CATALOG.PRIMARY_KEYS and V_CATALOG.FOREIGN_KEYS tables contained incorrect values in their ORDINAL_POSITION columns. In both tables, this column contained the positions of the key columns within their table, not their positions within the primary or foreign key. As a result, metadata queries for the ADO.NET, JDBC and ODBC drivers returned incorrect positions for columns within keys. This problem has been corrected in the Vertica server's V_CATALOG tables, and Vertica's drivers now return the correct key column positions as a result.

VER-27640

Client Drivers - Misc

With IPVS, clients could not connect to the cluster through virtual IP if the slave director went down. This issue has been resolved.

VER-26318

Client Drivers - ODBC

For some locales, the ODBC drivers could incorrectly convert double values, or throw an exception during the attempted conversion. This issue has been resolved.

VER-27447

Client Drivers - ODBC

Previously, the ODBC driver did not recognize certain aliases for connection properties when SQLConnect() was called (all aliases worked with SQLDriverConnect()). This problem has been corrected.

VER-28990

Client Drivers - ODBC

Connections associated with result sets returned by multi-statement queries were incorrectly handled. This issue has been resolved.

VER-29283

Client Drivers - ODBC Previously, the Windows ODBC driver did not support the use of named pipes with COPY LOCAL statements. Support for this feature has been added.

VER-23508

Client Drivers - VSQL Using a command such as the following from a vsql client (to pipe a .gzip file to a COPY from LOCAL statement) failed with an error: cat "/tmp/Test1V6B_50.gz" | vsql -h myhost -U dbadmin -d VMart -c "copy customer_DATA from local STDIN GZIP DIRECT ;" ERROR 0: COPY: Error occurred during ZLIB decompression. ZLIB error code: -3, Message: incorrect header check. This problem has now been fixed to support Linux and Windows platforms.

VER-23602

Communications/ messaging Vertica 7.0.0 includes improved transaction commit performance.

VER-26262

DDL Previously, running EXPORT_OBJECTS failed if you explicitly specified a view with dependencies on other views that were not included in the export. This problem has been resolved.

VER-26499

DDL Users who had created a role or a user called DBDUSER in previous releases encountered an issue when upgrading to version 6.0.x or later. The database did not start and Vertica issued an error: DBDUSER should be a predefined role. This issue has been resolved. Vertica now issues a warning instead, and informs the user that only the DBADMIN will be able to run Database Designer

VER-27953

DDL - Projection A CREATE PROJECTION statement, creating prejoin projections, caused the database to fail when the statement checked whether the segmentation expression contained long string attributes.

VER-27817

DDL - Table Previously, CREATE TABLE LIKE did not copy the default column value of the source table. In Vertica 7, as long as the default value expression does NOT reference a sequence, it will be copied to the target table.

VER-26487

Data Removal - Delete, Purge, Partitioning Partition keys that were not VARCHAR or INTEGER types occasionally resulted in a "Too many partitions" error. This issue has been resolved. If CREATE TABLE encounters an expression that may result in an invalid partition key value, a warning displays but CREATE TABLE execution continues.

VER-27493

Data Removal - Delete, Purge, Partitioning Previously, PURGE failed if there were temporary tables in the database. This issue has been resolved. If your database contains temporary tables, the PURGE function displays a warning but continues executing. Vertica does not purge temporary tables.

VER-27795

Data Removal - Delete, Purge, Partitioning Previously, calling the MOVE_PARTITION_TO_TABLE() function required CREATE privilege on schema, even if the target table already existed. This issue has been resolved. Vertica requires USAGE privileges if target table exists and CREATE privileges if the table does not already exist.

VER-21523

Data load / COPY Vertica fails when it should error out in certain cases when doing an Import/Export between two clusters with an improper network configuration between the two clusters.

VER-25732

Data load / COPY While loading data using a UDL, changing the ForceUDxFencedMode configuration parameter during query processing could cause a PANIC error. This has been resolved.

VER-26623

Data load / COPY If COPY cannot locate a specified record terminator (possibly due to mistyping the character), COPY searches for the character until it runs out of memory. The OUT OF MEMORY message now includes a HINT to double-check the record terminator.

VER-26643

Data load / COPY In this release, Vertica resolved several issues related to node stability when using the COPY LOCAL statement.

VER-27753

Data load / COPY When running the statement ALTER NETWORK INTERFACE..RENAME TO for a target network interface whose name already existed, Vertica displayed the name incorrectly in the resulting error message. This issue has been resolved.

VER-28465

Data load / COPY Using COPY LOCAL to load files whose size is an exact multiple of 1MB (to the byte), caused an internal error. This issue has been resolved.

VER-25978

Database Designer Core Database Designer failed because an "OFFSET" clause was incorrectly added to a CREATE TABLE statement during database design. This issue has been resolved.

VER-29260

Database Designer Core Queries on V_MONITOR.COLUMN_STORAGE sometimes experienced performance problems. This issue has been resolved.

VER-30373

Documentation The Vertica 7.0.x documentation incorrectly stated that the MERGE_PARTITIONS function was deprecated and removed from the product. The function is actually obsolete and will be deprecated in the next release. The documentation has been corrected.

VER-26006

Execution Engine In rare circumstances, when network connectivity between nodes failed during query plan setup (typically in a noisy networking environment), an individual Vertica node sometimes failed. This issue has been resolved.

VER-26062

Execution Engine When users issued an UPDATE or DELETE statement with IS NULL in the query when a database node was down, the following error sometimes occurred: Vertica Internal Error 12 '0 == "Unexpected data type for makeIsNull"' This issue has been resolved.

VER-26118

Execution Engine Mixing two different numeric types in a SQL statement no longer causes an error message to be added to the V_MONITOR.ERROR_MESSAGES table.

VER-28484

Execution Engine Queries containing multiple analytics functions on different partition keys showed different results for one of the analytic functions depending on the order of the analytic function in the SELECT statement. This issue has been resolved.

VER-26586

Front end - Parse & Analyze In previous releases, the UPPER function gave an error about exceeding the maximum octet length. This issue has been resolved.

VER-27082

Front end - Parse & Analyze Using NULLIF with aggregate functions sometimes produced incorrect results. This issue has been resolved.

VER-27310

Front end - Parse & Analyze Running SELECT statements with invalid hints caused Vertica nodes to fail. This issue has been resolved.

VER-28906

Hadoop The HDFS connector could wait on unresponsive HDFS DataNodes indefinitely instead of timing out. To control timeouts, three optional parameters have been added to Vertica's HDFS source. connection_timeout - Sets the maximum number of seconds to wait for the HDFS server to accept the connection before timing out. The default is 60 seconds. low_speed_limit - Sets the minimum data transfer rate in bytes per second. If the data transfer rate is below this minimum for the amount of time set for parameter low_speed_time, the HDFS connector times out. The default is 64 kilobytes per second. low_speed_time - Sets the maximum time the transfer rate is allowed lower than parameter low_speed_limit before the HDFS connector times out. The default is 60 seconds.

VER-26274

Installation - Package (rpm/deb) If you are upgrading from Management Console versions 6.1.1 or earlier, you must use the system kill command on SUSE systems to stop the Management Console Java process before upgrading to Management Console 7.0.

VER-29878

Installation - Package (rpm/deb) Customers who used the beta version of the Java UDx package must remove the Java package before upgrading to Vertica 7. The Java UDx functionality is now included in the server.

VER-17446

Installation Program If you supply the install_vertica script with a database administrator account that has no Linux password, the installation or upgrade fails after prompting you multiple times for passwords.

VER-23905

Installation Program The Vertica installer did not check for the presence of the required bash shell and attempted to perform the installation even if the shell was not present. This issue has been resolved.

VER-25105

Installation Program The Vertica installer incorrectly warned that CPU scaling was enabled when no scaling module was loaded. This issue has been resolved.

VER-25226

Installation - Package (rpm/deb) Installation Program Vertica installation scripts no longer use the 'bc' program and its requirement has been removed from the RPM/Debian packaging.

VER-25339

Installation Program The Vertica installer incorrectly printed an informational message advising the user to install pstack when pstack was already installed. This issue has been resolved.

VER-26375

Installation Program The Vertica installer did not work correctly on some locales. This issue has been resolved.

VER-27421

Installation Program Some operating systems use group names that affect the output of a standard df command, resulting in an error. This issue has been resolved.

VER-27958

Installation Program The install_vertica script did not fail if it was incorrectly passed the Management Console RPM. This issue has been resolved.

VER-28808

Installation Program Trying to add a node that was unreachable by SSH to the cluster caused the database to fail. This issue has been resolved.

VER-26035

Logging When creating a database, the dbadmin password was saved in cleartext in bootstrap-catalog.log. This issue has been resolved.

VER-25880

Management API (Session Mgmt, Shutdown) If during shutdown the Last Good Epoch (LGE) is behind (typically a result of an error during moveout), shutdown will abort with an error message, giving the user an opportunity to fix the issue without losing data.

VER-28019

Metadata Tables In previous releases, query string output from the V_MONITOR.QUERY_PROFILES table erroneously included newlines and tabs. This issue has been resolved.

VER-28752

Optimizer In certain situations, queries that perform merge joins did not return correct results. This issue has been resolved.

VER-29075

Optimizer Junk values resulted when using SUM and CAST together in a nested CASE. This issue has been resolved.

VER-29259

Optimizer ANALYZE_STATISTICS sometimes caused Vertica to fail when it should have returned an error message. This issue has been resolved.

VER-25886

Recovery In previous releases, during node recovery, an S-lock was placed on every table during current phase, preventing table inserts, updates, or deletes until recovery was complete. Node recovery has changed to implement a T-lock on every table during current phase, which permits concurrent inserts. T-locks preclude update and delete statements, and table DDL, such as dropping partitions or truncating tables.

VER-16658

ResourceManager Insufficient resource error messages are unclear. This issue has been resolved.

VER-24535

ResourceManager Queries are sometimes forced to queue due to MAX_CONCURRENCY limit, even though fewer than the maximum number of queries are active against the pool.

VER-26536

ResourceManager Vertica can run more slowly when querying columns with many views. This issue has been resolved.

VER-26573

ResourceManager Inter-node query plan messages that were very large (hundreds of megabytes, or gigabytes in size) are now compressed to avoid a previous internal size limit that could cause queries to be cancelled with an "invalid buffer enlargement request size" error.

VER-27779

ResourceManager ALTER RESOURCE POOL EXECUTIONPARALLELISM did not accept DEFAULT as input. This issue has been resolved.

VER-29205

ResourceManager Under heavy load, the Vertica memory allocator could cause a server failure. This problem has been resolved.

VER-25901

SDK User-defined analytic functions in fenced mode sometimes caused Vertica to fail. This issue has been resolved.

VER-28622

Security If you had LDAP enabled over SSL/TLS and the LDAP connection string was incomplete or invalid, you were still allowed to connect to the LDAP server. This issue has been fixed in Vertica 7.0. If you are upgrading from 6.1 to 7.0, you need to make changes to the ldap.conf file and the LDAPCONF environment variable before upgrading. "Configuring LDAP Over SSL/TLS When Upgrading Vertica" in the Installation Guide describes the changes to make to either use the more-secure 7.0 behavior or the less-secure 6.1 behavior.

VER-29265

Data Removal - Delete, Purge, Partitioning System:Performance Performance of DELETE statements has been improved in version 7.0.

VER-29268

System:Stability Cancels performed during a very brief window during a transaction can cause a failure to acquire the global catalog X lock during the commit phase of a transaction. This issue has been resolved.

VER-18489

Third Party Tools Integration The Vertica 7.0.x Informatica plugin now generates an error message with invalid pre/post SQL queries.

VER-26369

Third Party Tools Integration The Vertica 7 Plug-in for Informatica resolves an issue where rows were inserted rather than deleted in target tables. See the Vertica 7.0.x Plug-in for Informatica Guide for more information.

VER-27680

Third Party Tools Integration When using the Vertica 7.x plug-in for Informatica, corrected an issue where exception messages were not displayed for failed loads through Informatica PowerCenter.

VER-27005

Transactions Vertica can fail when a user brings down one node in a three node cluster. This issue has been resolved.

VER-26305

UI - Agent Previously, the /etc/init.d/vertica_agent command script returned an incorrect status exit code of 0 when the agent was not running. This issue has been resolved. The command now returns the correct exit code 3 in those conditions.

VER-28108

UI - Management Console UI - Agent Users were sometimes unable to import a database to Management Console. This issue has been resolved.

Known issues and limitations in Vertica 7.0.x

Updated: August 22, 2014

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.

Known issues

Issue

Component

Description

VER-29394

Catalog Engine Backup/DR

Cancelling the vbr.py script does not close the session or release locks.

VER-29818

Backup/DR

Schema level backups fail if a temporary table exists at the checkpoint epoch of the super projection.

Workaround:
Drop the temporary table and perform the backup again.

VER-29800

Client Drivers - ODBC

When returning SQL_SUCCESS_WITH_INFO, the Vertica ODBC client does not return the additional information.

VER-30409

Documentation

The Vertica 7.0.x Installation Guide incorrectly states that Management Console requires a separate node. In Vertica 6.1.3 and later, Management Console can be installed on any node in the cluster.

VER-30187

Documentation

In the Vertica 7 documentation, links that go from one PDF to another PDF are broken.

Workaround:
Cross-book links work correctly in the Vertica 7 Webhelp. To access, go to www.vertica.com/documentation and choose Vertica 7 Online Documentation.

You can also download and install documentation locally.

VER-29404

Optimizer

For some queries, the optimizer joins tables on a skewed column and uses the join as an Inner join in a hash join. This situation can cause query replanning and slow performance.

Workaround:
Set the ForceEarlyMaterialization flag to True to force the join to function as an Outer Join and improve performance.

VER-30118

Performance tests

Vertica may underestimate planning resources for queries with LONG VARCHAR or LONG VARBINARY in clusters with many nodes. This could result in swapping.

Workaround:
Lower the value in MAXMEMORYSIZE in the general resource pool.

VER-25768

Recovery

Databases with K Safety = 0 may not recover successfully after unexpected system failure.

Workaround:

HP requires that all production databases have a minimum K-safety of one (K=1). HP also recommends taking frequent backups.

VER-29360

Transactions

A race condition can sometimes cancel a drop partition operation instead of the internal mergeout session.

Workaround:
Retry the drop_partition operation.

VER-29648

UI - Management Console

The OK button on the warning dialog that appears after a user creates a problem cluster with Management Console does not work.

Workaround:
Click the X to close the dialog.

VER-29727

UI - Management Console

If you create a database immediately after creating a cluster, the second page of the database creation remains hidden.

Workaround:
Tab to the hidden page and try again.

VER-29733

UI - Management Console

After starting a database using Management Console, users could not retrieve chart data.

Workaround:
Log out of the Management Console and log back in. You can also restart Management Console to correct the problem.

VER-29738

UI - Management Console

Management console users who are mapped to Vertica users that do not have at least the dbadmin role set as a default role will not see activity charts as they might expect.

Workaround:
Vertica security requires that a role be set as a default role if the privileges are to be used automatically in each session.


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 - 2015 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