Release Notes

Vertica
Software Version: 7.2.x

 

Updated: May 5, 2017

 

About Vertica Release Notes

Security Warnings

Vertica 7.2.3-19: Resolved Issues

Vertica 7.2.3-18: Resolved Issues

Vertica 7.2.3-17: Resolved Issues

Vertica 7.2.3-16: Resolved Issues

Vertica 7.2.3-15: Resolved Issues

Vertica 7.2.3-14: Resolved Issues

Vertica 7.2.3-13: Resolved Issues

Vertica 7.2.3-12: Resolved Issues

Vertica 7.2.3-11: Resolved Issues

Vertica 7.2.3-10: Resolved Issues

Vertica 7.2.3-9: Resolved Issues

Vertica 7.2.3-8: Resolved Issues

Vertica 7.2.3-7: Resolved Issues

Vertica 7.2.3-6: Resolved Issues

Vertica 7.2.3-5: Resolved Issues

Vertica 7.2.3-4: Resolved Issues

Vertica 7.2.3-3: Resolved Issues

Vertica 7.2.3-2: Resolved Issues

Vertica 7.2.3-1: Resolved Issues

Vertica 7.2.3: Resolved Issues

Vertica 7.2.2-3: Resolved Issues

Vertica 7.2.2-2: Resolved Issues

Vertica 7.2.2-1: Resolved Issues

Vertica 7.2.2: Resolved Issues

Vertica 7.2.1-5: Resolved Issues

Vertica 7.2.1-4: Resolved Issues

Vertica 7.2.1-3: Resolved Issues

Vertica 7.2.1-2: Resolved Issues

Vertica 7.2.1-1: Resolved Issues

Vertica 7.2.1: Resolved Issues

Vertica 7.2.0-1: Resolved Issues

Vertica 7.2.0: Resolved Issues

Vertica 7.2.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.2.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/7.2.x/HTML/index.htm.

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 access the ftp site using the credentials available in the Vertica Hotfix release notice email.

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

Vertica 7.2.3-19: Resolved Issues

Release Date: 5/5/2017

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

Issue

Component

Description

VER-53727

Backup/DR

This fix removes an incorrect warning message during vbr replication.
VER-53241 Catalog Engine In rare cases, updating a table that had failed to commit caused an assertion due to incomplete catalog cleanup.

VER-53532

Cloud - Amazon

COPY loads from S3 failed in an error if authentication occurred more than 15 minutes before the HTTP GET request was made.

VER-50005

Execution Engine

If an input file was truncated during User-Defined Load, Vertica failed to invoke the UDParser, preventing a number of rows from loading.

VER-52909

Execution Engine

Using the keyword CASCADE with ALTER TABLE DROP CONSTRAINT did not drop dependent foreign keys.

VER-53565

Kafka Integration

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

VER-53246

Optimizer - Plan Stability

If used with multiple commands, a client connection using the vsql -c option sometimes generated an error when retrying queries.

VER-53689

Refresh

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

VER-52912

Sessions

It was possible for enforcement constraint checks for single-row INSERT statements to introduce an incorrect catalog snapshot. This issue sometimes caused incorrect assertions or incorrect query results.

Vertica 7.2.3-18: Resolved Issues

Release Date: 4/17/2017

Vertica has introduced hotfix 7.2.3-18 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-53625

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.2.3-17: Resolved Issues

Release Date: 4/4/2017

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

Issue

Component

Description

VER-52714, VER-51997 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-51219 Backup/DR If a table dropped an AUTO_INCREMENT or IDENTITY column, and was moved from the schema where it was created to another schema, restoring the table caused node failure.
VER-52504 Backup/DR Vertica 7.2.3-15 and later failed to clean up a temporary directory created during backup.
VER-51998 Backup/DR Vertica sometimes reassigned ownership of objects incorrectly when restoring or replicating tables in CreateOrReplace mode.
VER-51439 Catalog Engine

In Vertica 7.2.x, creating multiple projections with the same basename, then running the merge_projections_with_same_basename() metafunction, could in some cases lead to internal errors or catalog corruption.

 

Vertica 7.2.3-17 resolves this issue, by replacing this metafunction with merge_unsegmented_projections(), which merges unsegmented projections on 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-53003 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-52682 Database Designer Core Running DESIGNER_DESIGN_PROJECTION_ENCODINGS on projections sometimes caused Vertica to incorrectly remove comments on those projections.
VER-52580 Execution Engine Inserting a Top-K projection sometimes failed if it contained long varchar columns.
VER-50888 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-52256 Hadoop Previously, Vertica did not check the size of a file immediately after writing it to HDFS, which sometimes caused data consistency issues. With this fix, Vertica produces an error and rolls back the transaction if a file size mismatch occurs.
VER-51858 Optimizer Under certain circumstances, involving complex cyclic joins, Vertica encountered an internal optimizer error.
VER-52999 Optimizer - Query Rewrite Aggregating CASE expressions of numeric type sometimes caused an internal server error.
VER-52958 UI - Management Console When a Management Console user that was mapped to a non-dbadmin Vertica user viewed MC charts, MC did not properly close connections to Vertica. This caused some charts to hang.
VER-49861 UI - Management Console Management Console encountered errors if the operating system language was set to Japanese.

Vertica 7.2.3-16: Resolved Issues

Release Date: 3/9/2017

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

Issue

Component

Description

VER-51337 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-49411 Diagnostics A bug in which Scrutinize failed to clean up processes on remote nodes has been fixed.
VER-51639, VER-51620, VER-51619, VER-51984 Execution Engine, Sessions During long-running sessions, Vertica sometimes held onto query level resources longer than necessary.
VER-52561 Execution Engine In rare circumstances, node failure could occur if a shared resource that was not guarded was accessed by parallel sessions.
VER-51216 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-51842 Kafka Integration An incorrect assertion within the UDFilter occasionally generated a false error, and in rare cases could cause the database to fail.
VER-51824 Tuple Mover Querying a table while performing data changing operations on it could produce incorrect results, due to inconsistent snapshots across nodes.

Vertica 7.2.3-15: Resolved Issues

Release Date: 1/20/2017

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

Issue

Component

Description

VER-51142 Admin Tools In rare cases, admintools timed out when adding new nodes to a cluster.
VER-51069 Backup/DR When backing up to shared storage, it was possible for vbr to treat the same actual location on a shared volume as different backup locations, which could cause corrupt backup files.
VER-51005 Backup/DR You can query tables without their fully qualified names (i.e schema.table) by setting the search_path. Such queries sometimes failed if a referenced schema was replicated concurrently.
VER-50853 Backup/DR The amount of time required to remove large numbers of ROS files from backups has been significantly improved.
VER-51028 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-51105 Data Removal - Delete, Purge, Partitioning, Vertica Log Text Search This fix makes it possible to move, swap, and copy partitions between two tables that have text indexes in non-public schemas.
VER-50966 Execution Engine, Optimizer The database sometimes failed when Vertica set the type modifier incorrectly in certain CASE statements with SQL macros.
VER-50268 Hadoop Sentry authorization sometimes failed when Vertica read Parquet files from HDFS. This issue has been resolved
VER-50374 Optimizer If any nodes were down, queries using predicates on live aggregate projections sometimes failed with an error.
VER-50970 Recovery Table recovery took an excessive amount of time when there was nothing to recover in the database. Now, tables with nothing to recover are marked as UP at the beginning of recovery.

Vertica 7.2.3-14: Resolved Issues

Release Date: 12/21/2016

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

Issue

Component

Description

VER-50837 Data load / COPY, Execution Engine INSERT queries with joins running as part of ETL took longer to complete in Vertica 7.2.3.
VER-47721 Kafka Integration Vertica now uses an upgraded rdkafka library that fixes a potential deadlock issue when closing rdkafka handles.
VER-50648 Client Drivers - JDBC When using JDBC, Vertica could convert time zones incorrectly if the input value for dstSavings did not match that of the current calendar.
VER-49069 Optimizer - Statistics and Histogram ANALYZE_STATISTICS returned no results for local temporary tables if their K-safety value was lower than the cluster’s.

Vertica 7.2.3-13: Resolved Issues

Release Date: 11/21/2016

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

Issue

Component

Description

VER-49418 Data load / COPY During decompression, LZO sometimes did not check if the input stream had enough bytes for the next stage of the operation. This caused an error when decompressing some files. This issue has been resolved.
VER-50257 Execution Engine Due to a race condition, Vertica sometimes lost some rows during loading, but did not produce an error message. This issue has been resolved.
VER-50190 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-48969 Hadoop Previously, a segmentation fault occurred if a Parquet file’s first row in a row group had a NULL decimal value. This issue has been resolved.
VER-50202 Hadoop When Vertica used external HDFS tables on many Hive partitions, Vertica could not query all the external HDFS tables' partitions, causing it to return in incorrect or incomplete results. This affected the WebHDFS and libhdfs++ connectors. This issue has been resolved.
VER-49662 Logging, Security Previously, you could query data for dc_ldap_link_events from only one node. This issue has been resolved.
VER-49837 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-50113 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-50098 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-45928 UI - Management Console Management Console could not discover the vioperf directory during cluster creation on a SUSE Linux Enterprise Server (SLES). This issue has been resolved.
VER-49793 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-49761 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 numbers “5450” 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.

Vertica 7.2.3-12: Resolved Issues

Release Date: 11/3/2016

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

Issue

Component

Description

VER-49304 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-49724 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-49430 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-49600 Recovery When applying a missed rollback event, Vertica sometimes collected all projections on node instead of collecting only those of the given table. This could cause internal errors or data inconsistency. This issue has been resolved.

Vertica 7.2.3-11: Resolved Issues

Release Date: 10/19/2016

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

Issue

Component

Description

VER-49299 DDL - Table 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-49387 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-49438 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 7.2.3-10: Resolved Issues

Release Date: 10/05/2016

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

Issue

Component

Description

VER-49084 Data Collector If Vertica updates a parameter that writes a Data Collector entry, while simultaneously attempting to write a Data Collector entry, a deadlock can occur. This issue has been resolved.
VER-49111 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-49140 Optimizer - Statistics and Histogram Previously, ANALYZE_STATISTICS failed on binary data columns. This issue has been resolved.
VER-49023 Security A confusing error message appeared when attempting to GRANT USAGE on a Resource Pool to a user. This issue has been resolved.
VER-49020 Security

In Vertica 7.2.3-7 through 7.2.3-9, an LDAP connection leak occurred during authentication. Over time, the leak may consume all LDAP connections, eventually preventing any new connections to the Vertica cluster and possibly affecting other services using the LDAP server. Vertica 7.2.3-10 fixes this issue. You should upgrade immediately if you use LDAP and are using an affected version of Vertica.

VER-48994 Refresh, Tuple Mover Tuple Mover did not correctly merge storage containers after a completed rebalance or after local segments were disabled. This issue has been resolved.

Vertica 7.2.3-9: Resolved Issues

Release Date: 9/26/2016

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

Issue

Component

Description

VER-48835 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-48785 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-48864 Optimizer Adding columns to tables with projections using expressions could cause the server to fail. This issue has been resolved.
VER-48859 Optimizer Queries on system tables with complex conditions sometimes produced non-deterministic results. This issue has been resolved.
VER-48858 Optimizer Merge joins on large tables in distributed node clusters sometimes hung. This issue has been resolved.
VER-48857 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-48861 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-48316 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-49003 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-48863 Refresh Adding columns to tables with User Defined Transform (UDT) projections, then refreshing the column, could cause an internal error. This issue has been resolved.
VER-48671 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-48973 UI - Agent, UI - Management Console A security issue in Management Console has been resolved.

Vertica 7.2.3-8: Resolved Issues

Release Date: 9/8/2016

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

Issue

Component

Description

VER-48700 Basics After setting the parameter TerraceRoutingFactor, Vertica could crash if you issued the SHOW DATABASE statement after you subsequently upgraded the database. This issue has been resolved.
VER-48707 Communications/messaging, 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.

 

Vertica 7.2.3-7: Resolved Issues

Release Date: 9/1/2016

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

Note: Do not use this version if you use LDAP to connect to Vertica as this version introduced VER-49020. VER-49020 is fixed in 7.2.3-10.

Issue

Component

Description

VER-47903 Backup/DR In Vertica 7.2.3, some vbr tasks incorrectly copied data one node at a time instead of in parallel. This issue has been resolved.
VER-48512 Backup/DR The vbr backup script would fail if it encountered a running rsync daemon without an rsync configuration file. This issue has been resolved.
VER-48388 Backup/DR In Vertica 7.2.3, the performance of object restore and replication tasks slowed, especially when restoring or replicating many objects. This issue has been resolved.
VER-48511 Client Drivers - ADO VerticaDataReader.GetString() incorrectly rendered empty string values as NULL. This issue has been resolved.
VER-48439, VER-48440 Execution Engine, 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-48499 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-48380 Security During shutdown, Vertica attempted to disconnect from the LDAP server twice, which sometimes caused a core dump. This issue has been resolved.
VER-48438 Sessions If you enabled a constraint with ALTER TABLE using different capitalization from that used to create the constraint, the constraint check did not find duplicate values. This issue has been resolved.

Vertica 7.2.3-6: Resolved Issues

Release Date: 8/24/2016

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

Issue

Component

Description

VER-48490 Execution Engine This fix provides HPE Vertica support staff with the ability to debug a large cluster performance issue that could not be reproduced in-house.

Vertica 7.2.3-5: Resolved Issues

Release Date: 8/17/2016

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

Issue

Component

Description

VER-48106 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-48297 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-47954 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-48164 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-48170 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-46812 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-47936 Security Deleting a role group on the LDAP server, then running sync, sometimes caused Vertica to fail. This issue has been resolved.
VER-48278 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.

Vertica 7.2.3-4: Resolved Issues

Release Date: 8/2/2016

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

Issue

Component

Description

VER-48027 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-48057 Data load / COPY Vertica did not clean up the empty rejected row files that COPY statements created. This issue has been resolved.
VER-47350 Data load / COPY Some successful COPY commands incorrectly generated an error: "Unable to deparse query command type: 5". This issue has been resolved.
VER-47351 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-47353 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-48033 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-47352 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-47810 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-47415 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-47993, VER-47992 Security, UI - Management Console Management Console did not allow multiple OU filters when using LDAP. This issue has been resolved.

Vertica 7.2.3-3: Resolved Issues

Release Date: 7/26/2016

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

Issue

Component

Description

VER-47425 AP-Geospatial ST_Intersects incorrectly evaluated some GEOMETRY objects as too complex. This fix improves the evaluation process.
VER-47348 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-47532 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-47831 Client Drivers - ADO In the Vertica ADO.net driver versions 7.2.2 and above, inserting multiple commands into a single statement without parameters failed with an error. This issue has been resolved.
VER-46175 Client Drivers - ODBC In the ODBC driver, SQL_DESC_OCTET_LENGTH returned incorrect results for char and varchar types in unicode. This issue has been resolved.
VER-47357 Database Designer Core Loading UPDATE and DELETE queries containing subqueries into the Database Designer for optimization caused internal optimizer errors. This issue has been resolved.
VER-47354 DBD Running multiple invocations of DESIGNER_DESIGN_PROJECTION_ENCODINGS in parallel sometimes generated an error. This issue has been resolved.
VER-47706 FlexTable In Vertica 7.2.3-2, copying timestamp values from Apache Avro to Vertica columns sometimes caused 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-47376 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-47515 Hadoop hcatUtil failed to copy jar files if the path name contained “test” or “source”. This issue has been resolved.
VER-47349 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-47594 ResourceManager In some circumstances, Vertica continually allocated unused virtual memory, which slowed performance. This issue has been resolved.
VER-47355 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-47356 Security Authentication sometimes failed due to a concurrency issue during LDAP setup, which caused the cluster to fail. This issue has been resolved.
VER-46781 Sessions In Vertica 7.2.3 through Vertica 7.2.3-2, 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-47492 UI - Management Console Attempting to import SSL certificates sometimes produced a blank dialog. This issue has been resolved.
VER-47497 UI - Management Console In Management Console, a success notification contained unnecessary fields. This issue has been resolved.
VER-47494 UI - Management Console Upgrading from Management Console 7.1.2-1 produced errors when restoring the configuration file. This issue has been resolved.
VER-47493 UI - Management Console Uploading SSL certificates in Management Console (MC) failed after upgrading from MC 7.2.x. This issue has been resolved.

Vertica 7.2.3-2: Resolved Issues

Release Date: 7/5/2016

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

Issue

Component

Description

VER-46849 AP-Geospatial In certain cases, ST_Intersects function returned incorrect results. This issue has been resolved.
VER-46717 Basics, Storage and Access Layer Previously, Vertica could unnecessarily consume blocks of memory that it would 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-45180 Catalog Engine, DDL Previously, Vertica took an exclusive global catalog lock while running a CREATE SCHEMA statement, even if the schema already existed. To improve performance, Vertica no longer takes the lock if the schema already exists.
VER-46241 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-46791 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-45866 Hadoop In Vertica 7.2.2, loading from the HDFS connector using HTTPS produced an error. This issue has been resolved.
VER-46391 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-46648 Kafka Integration The Kafka CLI produced errors during Microbatch validation due to unclosed ResultSets. This issue has been resolved.
VER-46649 Refresh During rebalance, an internal statement runs a system table query to compute the size of all projections (REBALANCE_CLUSTER) or all projections anchored on a table (REBALANCE_TABLE). This query can significantly increase the time it takes to rebalance. This fix introduces a configuration parameter, RebalanceQueryStorageContainers, which disables this potentially slow query. By default, RebalanceQueryStorageContainers is set to true, which enables the system table query.
VER-46731 SDK

Vertica 7.2.3-2 fixes 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. 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);
  3. Verify the LGE has advanced after you have dropped all DFS files. If it has advanced, you can safely upgrade to Vertica 7.2.3-2.
NOTE: Use caution whenever using DFS_DELETE. Hewlett Packard Enterprise recommends avoiding using this command when possible.

Vertica 7.2.3-1: Resolved Issues

Release Date: 6/7/2016

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

Issue

Component

Description

VER-46179

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-45829 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-45904 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-45924 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.

Vertica 7.2.3: Resolved Issues

Release Date: 5/20/2016

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

Issue

Component

Description

VER-43536

Backup/DR

The copycluster task included data that did not require copying in its progress information. This issue has been resolved.

VER-44194

Backup/DR

Vertica batched files inefficiently for copycluster tasks, slowing the performance of those tasks. This issue has been resolved.

VER-44227

Backup/DR

Object restore failed when the backup contained a table with a dropped identity column where the identity sequence was contained in another schema. This issue has been resolved.

VER-45156

Backup/DR

Previously, vbr sometimes failed on large clusters due to handling of a large number of open file descriptors. This issue has been resolved.

VER-40753

Client Drivers - ADO

When COMMIT came before RETURNREJECTED at the end of a COPY statement the command was not executed. The client now rewrites the COPY statement so that RETURNREJECTED is in the appropriate position if COMMIT or NO COMMIT are included.

VER-42414

Client Drivers - ADO

Previously, queries with comments containing question marks caused an exception to be raised and the query to fail. This issue has been resolved.

VER-36742

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

Client Drivers - JDBC

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

VER-44293

Client Drivers - JDBC

Calling the Vertica JDBC driver cancel method could fail on a statement taking a long time to complete. This issue has been resolved.

VER-42925

Client Drivers - ODBC

When using the ODBC client driver, executing a prepared SQL statement that inserted values into multiple columns sometimes resulted in an error if you inserted values using the DEFAULT keyword. This issue has been resolved.

VER-44109

Client Drivers - ODBC

The Vertica driver installation package failed on Windows Server 2012 R2 if you did not have the .NET Framework 3.5 SP1 feature turned on. This issue has been resolved. The driver installation package now turns on the .NET Framework 3.5 SP1 feature as part of the driver installation, if necessary.

VER-35796 DDL - Projection If you created a segmented projection on a K-safe system and omitted the KSAFE keyword, Vertica did not create buddies for the projection. The projection was unsafe and could not be refreshed. This issue has been resolved. With this fix, if CREATE PROJECTION omits KSAFE for a segmented projection, Vertica automatically applies system K-safety to the projection definition and creates the required number of buddy projections.

VER-41921

DDL - Projection

Previously, Vertica rolled back an ALTER TABLE ... ADD COLUMN statement if you attempted to add a column to a table that included a live aggregate projection. This issue has been resolved.

VER-44485

DDL - Projection

After upgrading from Vertica 5.x to 7.x, Vertica sometimes incorrectly generated errors instead of an informational message if you attempted to create an existing projection using CREATE PROJECTION IF NOT EXISTS. This issue has been resolved.

VER-45654

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

Data Removal - Delete, Purge, Partitioning

While purging data, the Tuple Mover sometimes incorrectly skipped storage containers on partitioned tables. This issue has been resolved.

VER-45655

Data Removal - Delete, Purge, Partitioning, Optimizer - Statistics and Histogram

Using MOVE_PARTITIONS_TO_TABLE to move partitions to a table that had no projections, put the database in an inconsistent state. This would generally cause system failure at some later point in time. This issue has been resolved.

VER-44608

Data load / COPY, FlexTable

In some cases, using the fcsvparser to load weblogs in a Flex table failed with the following error message: ERROR 6085: Unexpected exception calling process() User Function in UDParser. This issue has been resolved.

VER-39845

Data load / COPY, Storage and Access Layer

Vertica would not issue a warning when users created, or were granted access to, external tables they would not be able read due to storage location permissions. This issue has been resolved.

VER-39404, VER-43223, VER-44047, VER-44379, VER-44648, VER-44839

Execution Engine

When the scan operator tried to access the SIPS sorted value list, the database sometimes failed. This issue has been resolved.

VER-44377

Execution Engine

Enabling invalid constraints using prepared statements sometimes caused the initiator node to fail. This issue has been resolved.

VER-45653

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

Execution Engine, ResourceManager

If a query’s join predicate order and column sort order were not the same in a projection, the query sometimes produced wrong results when join spill occurred. This issue has been resolved.

VER-39615

FlexTable

The JSON parser sometimes failed with arrays containing more than 65000 entries. This issue has been resolved.

VER-45095

Hadoop

Reading multi-byte UTF-8 values from ORC files into a smaller-length string sometimes caused the last character to be malformed. This behavior has been corrected.

VER-40005, VER-43074

Optimizer

When high (10+) numbers of queries launched concurrently, they created a bottleneck at the query planning stage that delayed query execution. Vertica 7.2.3 significantly improves query planning throughput.

VER-43202

Optimizer

Queries returned an error when they were executed on a cluster with Terrace Routing enabled because the query plan included successive send/receive operations. Vertica 7.2.3 resolves this issue.

VER-43408

Optimizer

Vertica did not support execution of queries such as the following in JDBC: select 1.1 union all select nvl(?,1.1) ; In this case, Vertica was unable to determine the typemod of '?'. With Vertica 7.2.3, you can now make a prepared statement with an undetermined type. The typemod is checked only when you insert values to replace the question mark.

VER-44357

Optimizer

Vertica could not refresh live aggregate projections that were identical except for different encodings on the same columns. This issue has been resolved.

VER-44774

Optimizer

APPROXIMATE_COUNT_DISTINCT returned inflated estimates when the exact row count ranged between 200K and 400K. This issue has been resolved.

VER-45417

Optimizer

The ORDER BY clause in an analytics OVER clause incorrectly allowed references to SELECT list aliases. Vertica 7.2.3 no longer allows these references.

VER-45457

Optimizer

Previously, delete optimization intermittently sometimes caused violations in data integrity. Version 7.2.3 disables delete optimization if analytic functions are involved and the result is not sorted on all result expressions.

VER-43201

Optimizer - Join & Data Distribution

Vertica incorrectly treated some equal predicates as join filters instead of join conditions if they were different character string types (for example CHAR and VARCHAR). This issue has been resolved.

VER-44189

Optimizer - Locale

The IN operator sometimes ignored locale information when comparing strings, which led to incorrect results. This issue has been resolved.

VER-23217

Recovery

The checkpoint epoch of a projection did not advance when the projection became safe as a result of a change in k-safety. This issue has been resolved.

VER-34968

ResourceManager

In some cases, running a query against a resource pool with CPUAFFINITYSET specified generated a warning message. This issue has been resolved.

VER-43640

Sessions, Transactions

Prior to this release, you could set the MaxQueryRetries configuration parameter at the database level (ALTER DATABASE <dbname> SET MaxQueryRetries = <n>). As of Release 7.2.3, you can also set the parameter at the session level (ALTER SESSION SET MaxQueryRetries = <n>).

VER-44449

Storage and Access Layer

The COMPACT_STORAGE meta-function could fail if the storage to compact exceeded 2GB. This issue has been resolved.

VER-40649

UI - Management Console

Some session cookies in Management Console presented a security vulnerability. This fix enables additional security for session cookies.

VER-40660

UI - Management Console

User sessions in Management Console did not expire upon closing the browser. With this fix, closing the browser window expires user sessions after one minute.

VER-44029

UI - Management Console

Previously, a query in Management Console could slow database performance when users were on the Overview page and the database contained a large number of projections. This issue has been resolved.

VER-44319

UI - Management Console

Previously, Management Console incorrectly exposed user information in the HTTP response of certain pages. This issue has been resolved.

VER-44783

UI - Management Console

Previously, Management Console incorrectly exposed user information in certain queries. This issue has been resolved.

Vertica 7.2.2-3: Resolved Issues

Release Date: 5/17/2016

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

Issue

Component

Description

VER-45195 Backup/DR Previously, vbr could fail on large clusters with large values of the concurrency parameter, due to handling of a large number of open file descriptors. This issue has been resolved.
VER-45235 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-45807

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-45680 Data Removal - Delete, Purge, Partitioning, Optimizer - Statistics and Histogram Using MOVE_PARTITIONS_TO_TABLE to move partitions to a table that had no projections put the database in an inconsistent state. This would generally cause system failure at some later point in time. This issue has been resolved.
VER-45375, VER-45204 Execution Engine When the scan operator tried to access the SIPS sorted value list, the database could fail. This issue has been resolved.
VER-45232 Execution Engine, ResourceManager If a query’s join predicate order and column sort order were not the same in a projection, the query could produce wrong results when join spill occurred. This issue has been resolved.
VER-45522 Optimizer Previously, optimized delete under circumstances could intermittently cause violations in data integrity. This fix disables optimized delete if analytic functions are involved and the result is not sorted on all result expressions.
VER-45347 Optimizer - Join & Data Distribution Vertica incorrectly treated some equal predicates as join filters instead of join conditions if they were different character string types (for example CHAR and VARCHAR). This issue has been resolved.

Vertica 7.2.2-2: Resolved Issues

Release Date: 4/12/2016

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

Issue

Component

Description

VER-45186

Backup/DR

In Vertica 7.2.x, backups would sometimes retain data from old restore points that should have been removed. This issue has been resolved.

VER-45132 Data Removal - Delete, Purge, Partitioning While purging data, in some cases the Tuple Mover could incorrectly skip storage containers on partitioned tables. This issue has been resolved.
VER-44927 Execution Engine Enabling invalid constraints using prepared statements sometimes caused the initiator node to fail. This issue has been resolved.
VER-44517 Storage and Access Layer The COMPACT_STORAGE meta-function could fail if the storage to compact exceeded 2GB. This issue has been resolved.

Vertica 7.2.2-1: Resolved Issues

Release Date: 3/30/2016

HPE has integrated hotfix 7.2.2-1 into the downloads page on my.vertica.com to address a performance regression in the initial Vertica 7.2.2 server. This issue has been resolved and the fix has been integrated into the current Vertica downloads.

Issue

Component

Description

VER-44609

Optimizer

Vertica 7.2.2 introduced a performance regression that significantly decreased throughput for concurrent queries. This issue has been resolved.

Vertica 7.2.2: Resolved Issues

Release Date: 3/30/2016

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

Issue

Component

Description

VER-36651

AP-Advanced, UDX

Previously, column aliases were not always passed correctly to user-defined extensions. This issue has been resolved.

VER-43290

Admin Tools

Previously, upon upgrading, Vertica would sometimes issue an error saying that the database failed to start-up. The error message was not correct, as the start-up had not actually failed but was in process. This issue has been fixed. Vertica no longer issues the message.

VER-43449

Backup/DR

Extracting selected objects from a backup sometimes caused the restore process to fail. This issue has been resolved.

VER-43517

Backup/DR

If you had VSQL_PASSWORD set in the environment, vbr used that password to connect to the database regardless of whether a password was set in the vbr config or entered on the console. With this fix, if you give vbr a password, vbr uses that password in preference to any set in the environment.

VER-43554

Backup/DR

Restore operations could sometimes fail with an error if Vertica encountered a catalog object that did not need to be restored. This issue has been resolved. Rather than an error, a warning message now appears indicating the object that was not restored, and the restore operation continues.

VER-26799

Basics

Vertica would sometimes repeatedly issue (or log) the warning, “Error scanning meminfo line,” which could cause confusion, but which did not indicate a substantive issue. Vertica no longer issues this message.

VER-43022

Basics

In the nodes system table, the value of export_address_family could appear as null for some nodes rather than 'ipv4' or 'ipv6', after upgrading a database from a release of Vertica earlier than version 7.1. While a null value did not impact the functioning of the database, the inconsistency in field values was confusing. This issue has been corrected. Nodes within a database now show consistent values for the field export_address_family.

VER-19181

Client Drivers - ADO, Client Drivers - JDBC, Client Drivers - ODBC, Front end - Parse & Analyze

When using prepared statements with a client connection to a Vertica server, the server returns an error if you attempt to use a “?” character in a regex pattern-matching query. This fix introduces the ability to use the “%” character in place of the “?” character.

VER-39690

Client Drivers - JDBC

Previously, when connecting to Vertica with a JDBC client connection and a specified port number, some specified port numbers were automatically set to the default port number, 5433. This issue has been resolved.

VER-43248 Client Drivers - Python Client Previously, the Vertica Python Client could only fetch a maximum of 300 rows from SELECT queries. This issue has been resolved, and there is now no limit on the number of rows returned.

VER-42561

Communications/messaging

A difference in timings between nodes coming up during catalog upgrade sometimes caused catalog corruption. This issue has been resolved. HPE strongly recommends the application of this update as soon as possible.

VER-41243, VER-41560, VER-39284, VER-39379, VER-40404, VER-41338, VER-41455, VER-41603, VER-41949, VER-42244, VER-43024, VER-43152, VER-43558

Communications/messaging, Data load / COPY, Execution Engine, Monitoring

Under specific circumstances, an issue with network multiplexing resulted in segmentation fault errors that caused node failure. This issue has been resolved. If you disabled network multiplexing as a workaround, enable it after upgrading to this fix.

VER-43531

DDL

Users dropped by a dbadmin while connected to a database could use indirect privileges to continue creating objects as long as the session persisted and roles remained the same. Committing those changes could cause the server to fail. This issue has been resolved.

VER-44010

DDL

In some situations, Vertica could not automatically replace a failed node with a replacement node that was on active standby. Automatic replacement would fail. This issue has been resolved.

VER-42685

Data Removal - Delete, Purge, Partitioning

After re-partitioning a table and reorganizing its data, Vertica sometimes did not reorganize all of the data according to the new scheme. Vertica would occasionally retain some data under the old partitioning scheme. This issue has been fixed.

VER-42957

Data load / COPY

If an exception was thrown during COPY LOCAL, a built-in filter attempting to allocate memory when COPY LOCAL re-ran the load stack could cause segfault under certain circumstances. This issue has been resolved.

VER-36825, VER-43096

Execution Engine

Sometimes a node would fail when attempting to allocate memory during a mergeout operation. This issue has been resolved.

VER-41008

Execution Engine

Memory requested by an operator sometimes greatly exceeded the reserved memory. This fix provides a more accurate calculation for reserved memory for certain operators.

VER-42986, VER-43960

Execution Engine

During primary and unique key enforcement, in some cases an error was incorrectly generated if column names contained spaces or other special characters. This issue has been resolved.

VER-42989, VER-43463, VER-43266

Execution Engine, Optimizer, Storage and Access Layer

When the scan operator tried to access the SIPS sorted value list, the database could fail. This issue has been resolved.

VER-43001

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.

VER-43264, VER-43265

FlexTable

In some cases, Vertica could fail during query rewrite for Flex tables with the following error: “ERROR 3852: Length for type varchar cannot exceed 65000” This issue has been resolved.

VER-43522

FlexTable

Certain flex table functions, such as FDelimitedParser, were able to access invalid memory regions in some cases. This could cause the node to fail. This issue has been resolved.

VER-26522

Hadoop

The export_tables and export_objects operations sometimes failed to complete because of delays in fetching data through the HCatalog Connector. These operations now exclude HCatalog tables by default, but if the request includes HCatalog tables they will be exported.

VER-44054

Hadoop

If a COPY statement using ORC files specified the columns in the wrong order, so that data types did not match, it could cause the node to crash. Mismatched types now report ERROR 6726 (Datatype mismatch) and do not crash the node.

VER-36422

Hadoop, Security

Defining an HCatalog schema did not previously check that the Hive data was accessible, so it was possible to define a schema that could not be queried. Vertica now reports an error when defining a schema in this case.

VER-42626, VER-43675

Installation Program, SDK

Under certain upgrade scenarios between 7.1.x and 7.2.x, Vertica package extension upgrades would temporarily fail without providing instructions for re-running the installation. This issue has been resolved with additional logging during database upgrade and enhanced documentation for using the admintools install_package function.

VER-42100

Kafka Integration

The Vertica Kafka ingestion rate did not always distribute evenly among multi-partitioned Kafka topics. This issue has been resolved.

VER-42941

Kafka Integration

Kafka COPY statements containing broker lists of more than 100 characters long caused the following error: "ERROR 4800: String of XXX octets is too long for type Varchar(100)" . This issue has been resolved.

VER-26947, VER-41854

Optimizer

Vertica did not optimize joins between two tables in cases where the tables were joined on foreign and primary keys with unique values, but only one of the tables was queried. This issue has been resolved.

VER-36552

Optimizer

In Vertica 7.1 and higher, CREATE TEMPORARY TABLE failed if the ODBC connector locale was configured with a non-binary collation--for example, en_US instead of en_US@collation=binary. This problem was resolved. However, Vertica advises users to update their OBDC locale setting to binary collations. Non-binary collations can sort strings differently, and this difference can yield unexpected results.

VER-41838

Optimizer

Internal errors sometimes occurred if queries with multi-level aggregates (MLAs) had HAVING clauses containing both grouping functions and complex GROUP BY expressions. This issue has been resolved.

VER-42409

Optimizer

Multilevel aggregation now supports SELECT ... DISTINCT and aggregate functions that specify the DISTINCT option (AVG, COUNT, MIN, MAX, and SUM).

VER-42583

Optimizer

Vertica generated a confusing error message when the OVER clause in a CREATE PROJECTION statement specified an incorrect ORDER BY expression. This message has been rewritten.

VER-42680

Optimizer

Previously, certain queries could cause a core dump if they failed due to type inconsistencies within the query plan, with the error “<WARNING> Vertica Internal Error 11 'isInputTypeCompatibleWithExpected(intype, vartype)”. This issue has been resolved.

VER-43535

Optimizer

In some cases involving multiple analytics with different PARTITION BY clauses, the input was wrongly not sorted and therefore could return incorrect results. This issue has been resolved.

VER-43903

Optimizer

Using the NTH_VALUE function with a LIMIT clause, and a non-constant value as the row_number parameter, sometimes caused the database to fail. This issue has been resolved.

VER-44079

Optimizer

Vertica would issue the error message, “INTERNAL 3594: Internal Optimizer Error (11),” if you created a table as select (CREATE TABLE AS SELECT), included a case expression in the select list, and the case expression included an implicit true/false expression in a when condition. This issue has been fixed.

VER-37222

Procedural Languages

In Vertica 7.1.0 and above, when non-superusers ran external procedures, a warning was sometimes generated. This issue has been resolved.

VER-43065

Recovery

The Last Good Epoch (LGE) could fall far behind the current epoch if a new table was created during node recovery. This issue has been resolved.

VER-32017

Refresh

You can now advance the Ancient History Marker (AHM) to an epoch that is greater than the cluster refresh epoch (the smallest refresh epoch among all cluster nodes). REFRESH_EPOCH column in V_MONITOR.SYSTEM table is now deprecated and is always set to -1.

VER-33553

ResourceManager

Previously, nodes would occasional fail as the result of intermittent errors in queries. To prevent such errors from causing nodes to fail, we added better error protection.

VER-43224

ResourceManager

Queries selecting from rejected-data tables often requested too much memory and impacted performance, even if the tables were empty. This fix reduces the width of the rejected_data column. This may truncate results in your existing queries. If so, use ALTER COLUMN to extend the width of the rejected_data column.

VER-43524

ResourceManager

Reducing MAXMEMORYSIZE or MAXCONCURRENCY of a pool while cascading was enabled could cause queries to fail due to insufficient resources, and in some cases caused the cluster to fail. This issue has been resolved.

VER-42673

Security

When loading data using the HDFS Connector, the load could fail if the username parameter was different from the cached principal. Vertica now ignores the username parameter in Kerberos authentication.

VER-42647 UI - Management Console When importing databases, database credentials were sent to the server in a potentially vulnerable format. This issue has been resolved.
VER-42950 UI - Management Console When updating passwords on the Management Console Database Settings page, passwords were previously sent in a potentially vulnerable format. This issue has been resolved.
VER-42995 UI - Management Console During Management Console setup, a MC configuration parameter was previously vulnerable to command injection. This issue has been resolved.

 

Vertica 7.2.1-5: Resolved Issues

Release Date: 3/15/2016

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

Issue

Component

Description

VER-44190 Security Vertica 7.2.1 enforced more rigorous validation on users in the system. This caused errors for previously created users upgrading to 7.2.1 and beyond. This issue has been fixed.

Vertica 7.2.1-4: Resolved Issues

Release Date: 2/25/2016

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

Issue

Component

Description

VER-43792 Backup/DR If you had VSQL_PASSWORD set in the environment, vbr used that password to connect to the database regardless of whether a password was set in the vbr config or entered on the console. With this fix, if you give vbr a password, vbr uses that password in preference to any set in the environment.
VER-43826 Backup/DR Restore operations could sometimes fail with an error if Vertica encountered a catalog object that did not need to be restored. This issue has been resolved. Rather than an error, a warning message now appears indicating the object that was not restored, and the restore operation continues.
VER-44008 Backup/DR Extracting selected objects from a backup sometimes caused the restore process to fail. This issue has been resolved.
VER-43737 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.
VER-43919 Optimizer In some cases involving multiple analytics with different PARTITION BY clauses, the input was wrongly not sorted and therefore could return incorrect results. This issue has been resolved.
VER-43957 Optimizer Using the NTH_VALUE function with a LIMIT clause, and a non-constant value as the row_number parameter, sometimes caused the database to fail. This issue has been resolved.
VER-43921 ResourceManager Queries selecting from rejected-data tables often requested too much memory and impacted performance, even if the tables were empty. This fix reduces the width of the rejected_data column. This may truncate results in your existing queries. If so, use ALTER COLUMN to extend the width of the rejected_data column.
VER-43961 Sessions Enabled primary keys and unique keys were not enforced on a command issued from a JDBC or ODBC prepared statement. This issue has been resolved.

Vertica 7.2.1-3: Resolved Issues

Release Date: 2/4/2016

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

Issue

Component

Description

VER-43590 FlexTable

If a column's default value depended on a Flex function, uninstalling the Flex library could cause a table to drop data. This issue has been resolved.

VER-43381 Optimizer Internal errors sometimes occurred if queries with multi-level aggregates (MLAs) had HAVING clauses containing both grouping functions and complex GROUP BY expressions. This issue has been resolved.

Vertica 7.2.1-2: Resolved Issues

Release Date: 1/20/2016

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

Issue

Component

Description

VER-43252 Data load / COPY

If an exception was thrown during COPY LOCAL, a built-in filter attempting to allocate memory when COPY LOCAL re-ran the load stack could cause segfault under certain circumstances. This issue has been resolved.

VER-42004 Execution Engine In rare cases, an issue with network multiplexing resulted in segmentation fault errors that caused node failure.
VER-43158 Recovery The Last Good Epoch (LGE) could fall far behind the current epoch if a new table was created during node recovery. This issue has been resolved.
VER-43214 SDK Previously, some UDx side processes did not close and instead remained as defunct processes. This issue has been resolved.

Vertica 7.2.1-1: Resolved Issues

Release Date: 12/22/2015

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

Issue

Component

Description

VER-42933 Security When loading data using the HDFS Connector, the load could fail if the username parameter was different from the cached principal. Vertica now ignores the username parameter in Kerberos authentication.
VER-42889 Execution Engine

Previously, an error could occur during pattern matching queries if the maximum memory given to the PCRE JIT stack was not sufficient.

This fix introduces a new parameter, PcreJitStackMaxSizeScaleFactor, which allows you to configure the scale factor for the upper limit of memory given to the PCRE JIT stack. The base value is 1 MB. For example, if you set PcreJitStackMaxSizeScaleFactor to 16, the upper limit of the memory given to the PCRE JIT stack is 16 MB. The default value of PcreJitStackMaxSizeScaleFactor is 32.

Note that the memory given to the PCRE JIT stack cannot exceed the OS stack memory. OS stack memory can be determined by running "ulimit -s".

Vertica 7.2.1: Resolved Issues

Release Date: 12/3/2015

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

Vertica 7.2.1: Resolved Issues

Issue

Component

Description

VER-41624 Catalog Engine In some cases, PANIC may occur when a node is dropped from a session while a temp table is created on the dropped node in a different session.
VER-41720 Catalog Engine In rare cases, when a user is dropped from a session while it tries to connect from another session, a core dump is generated.

VER-42499

Client Drivers - ODBC

Using the ANALYZE_CONSTRAINTS function through an ODBC connection on a table with no constraints defined resulted in a misleading error message. This issue has been resolved.

VER-42309

Communications/messaging

A difference in timings between nodes coming up during catalog upgrade sometimes caused catalog corruption. This issue has been resolved. HPE strongly recommends the application of this update as soon as possible.

VER-42393

Communications/messaging, Execution Engine

Diagnostic messaging for connection failures has been improved. This also decreases the possibility of a False-Negative.

VER-42290

DDL, Optimizer

If you invoked CREATE EXTERNAL TABLE statement as a vsql command directly from the command line, it failed if preceded by another SQL statement. This problem has been resolved.

VER-40552

Data load / COPY, Data Removal - Delete, Purge, Partitioning

SQL queries with empty hint markers (/*+ */) could result in a node failing. This behavior has been corrected and empty hint markers are now ignored.

VER-39626

Data load / COPY, Hadoop

Copying through the HDFS Connector sometimes failed with error 3399 if a wildcard was used and the location contained empty files. This failure no longer occurs.

VER-31456

Execution Engine

Analytic functions PERCENTILE_CONT and PERCENTILE_DISC were refactored to perform faster. Query plans now avoid unnecessary sorting, and percentile functions with the same analytic clauses are now processed together.

VER-38609

Execution Engine

During deserialization of plans, segfault could occur due to an internal I/O error. This issue has been resolved.

VER-41307

Execution Engine

The Vertica resource checker now retains query plan audit records.

VER-41772 Execution Engine In some cases, a node can panic during shutdown if a user concurrently runs SELECT get_expected_recovery_epoch().

VER-42565

Execution Engine

Flawed locking logic during SIPs processing sometimes caused segmentation faults. This issue has been resolved.

VER-42203

Hadoop

Occasionally, when copying data from Hadoop with the HDFS Connector, the COPY query hung and could not be terminated with CLOSE_SESSION(). This issue has been resolved.

VER-28840

Installation Program

Previously, the installer checked the I/O scheduler for all volumes. With this fix, the installer only checks the I/O scheduler for volumes that host the datadir.

VER-42327

Kafka Integration

Previously, the Kafka Avro parser did not properly allocate memory. This issue has been resolved.

VER-25569

Optimizer

When running the ANALYZE_STATISTICS function to collect statistics on multiple tables, ANALYZE_STATISTICS could fail with an error message if one or more tables were concurrently dropped. This issue has been fixed. ANALYZE_STATISTICS succeeds, and produces a warning rather than an error.

VER-38980

Optimizer

Rounding logic of TIMESERIES clause is now documented in Analyzing Data in the Vertica documentation.

VER-41428

Optimizer

Vertica threw a confusing error message when the OVER clause in a CREATE PROJECTION statement specified an incorrect ORDER BY expression. This message has been rewritten.

VER-41081

Optimizer, Security

Previously, MERGE or COPY could not be performed on a table column that contained an Access Policy. You can now perform MERGE or COPY on a column if the enabled access policy allows you to access all the data in the column.

VER-36837

SDK

UDx failures sometimes occurred if REGEX_COUNTs were used when copying data from Hadoop with the HDFS Connector. This issue has been resolved.

VER-38152

Security

Previously, non-database administrator users could access system tables. This issue has been resolved with the implementation of the RestrictSystemTables security parameter.

VER-42132

UDX

This fix eliminates unnecessary exception handling messages in the log file.

VER-42137

UDX

External procedures that wrote over 255 characters to standard output and returned a nonzero exit code caused the UDx zygote process to fail. This issue has been resolved.

VER-42319 Vertica Log Text Search All UDx's for text search were previously saved in a schema named Txtindex. With this release, the internal schema is renamed to v_txtindex.

Vertica 7.2.0-1: Resolved Issues

Release Date: 11/18/2015

HPE has integrated hotfix 7.2.0-1 into Vertica downloads to address a serious 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.

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

Issue

Component

Description

VER-42265 Backup/DR When the length of an object is passed to a worker process, xmlrpclib.py produces an overflow error if the length of the object is larger than 2 GB. This issue has been resolved.

VER-42005

Catalog Engine

In some cases, PANIC could occur when a node was dropped from a session while a temp table was created on the dropped node in a different session. This issue has been resolved.

VER-42532 Communications/messaging A difference in timings between nodes coming up during catalog upgrade sometimes caused catalog corruption. This issue has been resolved. HPE strongly recommends the application of this update as soon as possible.
VER-41898 UDX If you developed a UDTF in Java or R and specified it in a live aggregate projection, execution of that projection could cause system instability. Similar behavior applied to UDSFs that were used as expressions in a projection. This issue has been resolved. Now, attempts to create live aggregate projections with unsupported UDTFs, and projections with unsupported UDSF expressions, fail with a warning message.

Vertica 7.2.0: Resolved Issues

Release Date: 10/21/2015

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

Upgrade Considerations

Previously, dialog was included in Vertica. Effective with 7.2.x, Vertica requires dialog to be installed on all nodes in the cluster before installing the database platform.

Vertica 7.2.0: Resolved Issues

HPE has integrated hotfix 7.2.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-40829

AMI

Previously, having transparent_hugepages set to "always" caused HPE Vertica to fail. This issue has been resolved.

VER-38268

Admin Tools

When creating a database on a two-node cluster, HPE Vertica would create the database but throw an exception upon trying to start the database. This issue has been resolved.

VER-40510

Admin Tools

Previously, the tmp directory permissions could interfere with database node startup. This issue has been resolved.

VER-39292 AdminTools HPE Vertica now requires dialog to be installed on all nodes in your cluster before installing the database platform.
VER-41093 Admin Tools, Installation Program Previously, the logrotate utility was not correctly rotating log files for some databases running on Red Hat Enterprise Linux 7. This issue has been resolved.

VER-28221

Backup/DR

The vbr backup tool could perform slowly in HPE Vertica implementations containing millions of small ROS files. This issue has been resolved.

VER-35746

Backup/DR

At the beginning of the of the backup process, HPE Vertica confirms that the number of existing backups does not exceed the limit specified in the restorePointLimit configuration parameter. If the addition of a backup archive would exceed this limit, vbr deletes the oldest existing archive. If you interrupt the backup process by pressing ^C before the newest archive is created, the oldest archive remains deleted. This process does not affect restore points as HPE Vertica always preserves the correct number of archives.

VER-36757

Backup/DR

When backing up a database using vbr.py, if the database was named "DB", then it would not display the node information in the output. This issue has been resolved.

VER-36859

Backup/DR

If external password files were used for backup or restore, the administrator had to copy the password files manually to all database nodes and backup hosts. With this fix, the vbr.py utility copies the password files automatically.

VER-36983

Backup/DR

In vbr.py, "ulimit -u" produced an error if unlimited was provided. This issue has been resolved.

VER-35716

Basics

Previously, HPE Vertica did not handle Moscow time correctly as Russia had updated the time zone, Moscow Time. This issue has been fixed.

VER-40146

Basics

The HPE Vertica server node allowed the client to make an SSL connection before the server node initialization completed. In some cases, the premature connection could cause the server to fail. This issue has been resolved.

VER-40940 Basics Previously, if you called the same UDx more than once in a SELECT statement, then each call to the UDx received the same parameter value that was passed to the first UDx call. This issue has been resolved.

VER-18296

Catalog Engine

Assigning node-specific identifiers for all instances of unsegmented projections did not scale well for large clusters. A single name now maps to all buddies of an unsegmented projection.

VER-18357

Catalog Engine

Projection creation in a database with a very large catalog sometimes timed out. This problem was tied to a wider issue of catalog scalability which this release addresses. Catalog size has been reduced by consolidating statistics storage, removing unused statistics, and storing unsegmented projection metadata once per database. This has significantly reduced overhead and bottlenecks associated with catalog size and usage.

VER-39198

Catalog Engine

Same as VER-39678

VER-40474

Catalog Engine

An assertion occurred if a historical query was run at a time that did not fall in the epoch range. The assert has been changed into an error.

VER-31953

Client Drivers - ADO

Previously, when executing multiple queries with parameters in a single connection via ADO.NET, an unsupported error was thrown. The error message now states that, "Inserting a compound statement with a parameter is not supported."

VER-35454

Client Drivers - ADO

Previously, attempting to use connection pooling with SSL enabled resulted in an error when a pooled connection was selected. This issue has been resolved.

VER-22487

Client Drivers - ADO, Client Drivers - JDBC, Client Drivers - ODBC, Communications/messaging

Previously, the driver handling of PROFILE statements was unreliable due to uncertainty about whether or not the statement being profiled should be expected to return a result set. This issue has been resolved.

VER-35683

Client Drivers - JDBC

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

VER-36005

Client Drivers - JDBC

Previously, using the display_license meta-function through a JDBC connection returned NULL. This issue has been resolved.

VER-36393

Client Drivers - JDBC

Previously, there was a case-sensitivity issue in the way the JDBC driver processed table and projection metadata for the KV feature. This issue has been resolved.

VER-37631

Client Drivers - JDBC

Previously, when using the JDBC driver, a compound statement that included a COPY LOCAL statement resulted in a server core dump. The JDBC driver no longer allows compound statements which include COPY LOCAL to be sent to the server. Instead, those statements throw an exception that is caught by the user's application. Additionally, users who upgrade their server version, but continue using a previously-released version of the JDBC driver, do not incur a core dump when executing this type of compound statement.

VER-37793

Client Drivers - JDBC

The JDBC driver encountered a deadlock caused by closing a connection when executing a query. This issue has been resolved.

VER-39708

Client Drivers - JDBC

The JDBC driver encountered a deadlock caused by closing a connection when reading table metadata. This issue has been resolved.

VER-39718

Client Drivers - JDBC

The HPE Vertica 7.1 server sometimes had an issue responding to the HPE Vertica 4.1 JDBC driver’s batch insert protocol, causing the server to fail. This issue has been resolved.

VER-35992

Client Drivers - ODBC

Previously, setting the Locale field in the DSN of an ODBC connection caused an error when ending the session. This issue has been resolved.

VER-35507

Client Drivers - VSQL

Previously, if vsql incurred an error while writing output to a file, but the disk ran out of space, vsql would fail silently. This issue has been resolved so that, when this error occurs, vsql displays an error message.

VER-35802

Client Drivers - VSQL

The performance of the \d operation in the vsql client has been improved for databases with large catalogs.

VER-34539

Communications/messaging

If a node left a cluster due to a network connectivity issue and went into a DOWN state, other nodes and admintools incorrectly saw it in SHUTDOWN state. This prevented restarting the node from admintools. This issue has been resolved.

VER-40546

DDL

In some cases, it was not possible to drop a column with a default expression referring to another column, even after dropping the default expression. This issue has been resolved.

VER-36066

DDL - Projection

When multiple CREATE PROJECTION statements with the "/*+createtype(L)*/" hint were issued simultaneously, the statements created projections with the same name, resulting in duplicate projections. This issue has been resolved.

VER-27177

Data Removal - Delete, Purge, Partitioning, Security

The requirement to grant truncate and drop privileges to a user has been resolved with the implementation of the new GRANT (Truncate) statement.

VER-35620

Data load / COPY

Bulk loading data using the COPY command sometimes resulted in sequence exceeded max value error. This issue has been resolved.

VER-36504

Data load / COPY

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

VER-37691

Data load / COPY

Removed log message that was not clear.

VER-35650

Data load / COPY, FlexTable

The issue where the database failed when running an INSERT/SELECT statement using a direct hint and the MAPCONTAINSKEY function has been resolved.

VER-35759

Database Designer Core

If a table had multiple unsegmented projections with unique definitions, rebalancing the cluster after adding new nodes caused only one of the projections to be replicated on the new nodes. The other unsegmented projections were ignored. Now, rebalance operations replicate all unique unsegmented projections across all nodes.

VER-36371

Database Designer Core

Database Designer threw a misleading error message "No existing projections found" on projections that were actually deployed. This behavior has been fixed.

VER-39572

Database Designer Core

Table names with embedded white space are now properly supported by database designer and REFRESH statement.

VER-35926

Error Handling

Previously, if you used the export_statistics function to export the table statistics of a table with no defined projection, subsequently trying to import statistics by performing an import_statistics would fail with an error message. This issue has been resolved.

VER-31503

Execution Engine

Previously, the timezone America/North_Dakota/Beulah was not recognized. This issue has been resolved.

VER-35741

Execution Engine

Some queries using a LIMIT clause sometimes incorrectly produced 0 rows of results. This issue has been resolved.

VER-36190

Execution Engine

Running the COUNT(DISTINCT) function negatively affected the performance of the APPROXIMATE_COUNT_DISTINCT function. This issue has been resolved.

VER-37481

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

Execution Engine, Optimizer, Query Generator

Previously, queries with CASE statements in predicates returned incorrect results. This issue has been resolved.

VER-36566

FlexTable

HPE Vertica now supports JSON keys greater than 255 bytes.

VER-36988

FlexTable

The issue where the database failed when running a MapDelimitedExtractor or MapJSONExtractor function when the NULL row is in WOS has been resolved.

VER-34062

Front end - Parse & Analyze

When using a fixed-length binary as a data type, queries were sometimes slow if an IN clause was used within the HEX_TO_BINARY function. This issue has been resolved.

VER-38618

Front end - Parse & Analyze

If an outer query referenced a subquery with a constant column and aggregate expression, and the outer query predicate included the constant column, the constant column sometimes was applied incorrectly to the subquery aggregation. This issue has been resolved.

VER-39537

Hadoop

The HDFS Connector failed if given a path with a non-terminal wildcard (for example, "/usr/*/foo"). It now properly handles such wildcards.

VER-40296

Hadoop

The HCatalog Connector did not support some Hive 0.13 data types. CHAR, VARCHAR, DATE, TIMESTAMP, and DECIMAL are now supported.

VER-41998 Hadoop The COPY statement sometimes failed to read ORC files from NFS partitions. This has been corrected.

VER-28007

Installation Program

sudo is no longer an installation dependency for new clusters.

VER-34620

Installation Program

The installer failed when network interfaces had the same name but different IP addresses. This issue has been resolved.

VER-36442

Installation Program

Previously, running 'sudo install_vertica' when sudo required a password could result in an installation failure. This issue occurred only when remote hosts required password authentication for sudo. This issue has been resolved.

VER-38043

Installation Program

Previously, HPE Vertica did not check if root was in the sudoers file before upgrading. This issue has been resolved.

VER-35948

Monitoring

If users made changes to Data Collector policies in HPE 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-30799

Optimizer

When a node is down, group-by prepass did not execute before the join, which considerably lengthens query processing. This issue has been resolved: when a node is down, a join is preceded by group-by prepass when group-by push-down conditions are satisfied.

VER-35740

Optimizer

New hint /*+add_vertica_option ()*/ enables ENABLE_WITH_CLAUSE_MATERIALIZATION option for a given query.

VER-35875

Optimizer

Queries ran slowly when an empty table (with zero rows) was set as the outer table in a join. This issue has been resolved so the empty table is set as the inner table in the join.

VER-35922

Optimizer

When grouping functions were aliased (for example: "grouping(c) as g1") they were not recognized as functions on aggregated data and were pushed down below aggregation, causing the HPE Vertica server to fail. This issue has been resolved.

VER-35963

Optimizer

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

VER-36142

Optimizer

Enclosing a TIMESERIES clause within a WITH clause caused an error. This problem has been resolved.

VER-36158

Optimizer

If an outer query referenced a subquery with a constant column and aggregate expression, and the outer query predicate included the constant column, the constant column sometimes was applied incorrectly to the subquery aggregation. This issue has been resolved.

VER-36593

Optimizer

A query with multiple RANGE clauses that operated on different data types returned an error. This issue has been resolved. 

VER-36621

Optimizer

When HPE 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.

VER-36695

Optimizer

Previously, SELECT statements with CAST did not work. This issue has been resolved.

VER-36858

Optimizer

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

VER-38332

Optimizer

An UPDATE statement with an inline view could incorrectly assign NULL values to a NOT NULL field. This issue has been resolved.

VER-39700

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

Optimizer - Statistics and Histogram

Previously, running IMPORT_STATISTICS and EXPORT_STATISTICS functions could fail when tables contained user defined data types. These functions now ignore columns with user defined data types.

VER-28290

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.

VER-35536

SDK

Using a User Defined Aggregate in a statement containing a GROUP BY clause may impact the performance of the aggregate function. This performance impact is caused by HPE Vertica passing the function one row of data per call. This release adds a special integer parameter named _minimizeCallCount that your UDA can declare to force HPE Vertica to batch several rows together before calling your UDA. This parameter can increase performance in cases where the overhead of invoking your UDA is greater than the overhead of having HPE Vertica batch the rows together. However, always test the performance of your UDA if you choose to add this parameter to ensure the performance has improved. See "UDA Performance in Statements Containing a GROUP BY Clause" in the Extending HPE Vertica guide for detailed information.

VER-36267

SDK

In some cases, calling a fenced-mode UDx within a CASE statement could cause HPE Vertica to exit with an error message. This issue has been resolved.

VER-40415

SDK

While executing external procedures, Vertica would sometimes hang in the fork() operation. This issue has been resolved. External procedures now execute in a separate process.

VER-34304

SDK-Java

Previously, the setNumericNull method didn't set output to a null value. Instead, the output was a random value. This issue has been resolved.

VER-35931

SDK-R

Previously, queries sometimes hung indefinitely when an R process failed. With this fix, queries terminate with an error.

VER-41919 SDK-R Two standard R packages, rpart and gbm, have been added to the HPE Vertica R Language Pack. The rpart package is not included in the HPE Vertica R Language Pack for Debian Linux 7.0 through 7.7 and Ubuntu 12.04 LTS and 14.04 LTS.

VER-20537

Security

Truncate privileges were limited to the table owner and superuser. This issue has been resolved with the implementation of Grant (Truncate) statement, which grants truncate privileges to non-owners of a table.

VER-27021

Security

The requirement to more efficiently grant users permissions to all objects in a schema has been resolved with the implementation of the new Inherited Privileges feature.

VER-33059

Security

Some users with dbadmin privileges were not able to view all rows in system tables. This issue has been resolved.

VER-34978

Security

The requirement for a specific user to view records in a query results table without granting the user the pseudosuperuser role has been resolved with the new System Monitor Role.

VER-35232

Security

The issue where GRANT SELECT ALL for tables in a schema was not implemented in any new tables in the schema has been resolved with the implementation of the Inherited Privileges feature.

VER-40138

Security

The version of Python shipped with the HPE Vertica package has been updated from Python release 2.7.0 to release 2.7.10, which includes fixes for Common Vulnerabilities and Exposures (CVEs). See the following link for the Python release notes: https://hg.python.org/cpython/raw-file/15c95b7d81dc/Misc/NEWS

VER-40779

Security

A user could create, but not select, from a view when permissions on the underlying table were granted via the PUBLIC role. This issue has been resolved.

VER-35873

Storage and Access Layer

The projection_columns table reported encoding types of GZIP_COMP and BZIP_COMP as unknown. This issue has been resolved.

VER-29360

Transactions

A DROP_PARTITION operation is expected to interrupt or cancel a conflicting MERGEOUT operation. In some instances the MERGEOUT operation did not cancel and the DROP_PARTITION timed out waiting for a table lock. Furthermore, a race condition in error reporting could sometimes result in a CANCEL error message being returned instead of the expected LOCK TIMEOUT error message. This issue has been resolved.

VER-36709

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. Furthermore, a race condition in error reporting sometimes caused incorrect TIMEOUT error messages when the server was actually successful in cancelling the MERGEOUT operation and proceeded with the DROP_PARTITION. This issue has been resolved.

VER-39678

Tuple Mover

When a large number of projections were eligible for mergeout, the Tuple Mover sometimes was slow to pick a mergeout job. This issue has been resolved.

VER-35421

UI - Management Console

Previously, when the Management Console was installed on an IPv6 system, it automatically started using that address even though Management Console does not support IPv6. With this fix, Management Console automatically starts on IPv4 address, which is supported.

VER-36025

UI - Management Console

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

VER-36700

UI - Management Console

In this release, tooltips were updated with more information about the Configuration Storage Location page in the Management Console setup wizard.

VER-37651

UI - Management Console

Database Designer in Management Console does not deploy designs if all queries are already optimized. Previously, the Deploy button was not hidden in these cases. This issue has been resolved.

VER-39347

UI - Management Console

Management Console previously performed continuous license audits, which could negatively affect performance of other queries. This issue has been resolved.

VER-40656

UI - Management Console

The issue where password credentials were being passed from the client to the server in plain text has been resolved.

VER-41117

UI - Management Console

In previous versions, upgrading Management Console (MC) on an HPE Vertica host required stopping the database if MC was installed on Ubuntu or Debian. You will still need to stop the database to complete the upgrade to hotfix 7.1.2-6 on these platforms. MC upgrades from versions 7.1.2-6 to future versions will no longer require stopping the database.

Known issues and limitations in Vertica 7.2.x

Updated: June 7, 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-43040 Client Drivers - ODBC ENABLE_WITH_CLAUSE_MATERIALIZATION is not supported for WITH CLAUSE prepared statements.
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.

 


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