Resolved issues
Resolved issues release notes for 9.2.x.
9.2.1-28
Release Date: 01/11/2022
| Issue Key | Component | Description |
|---|---|---|
| VER-80173 | Kafka Integration | Security vulnerabilities CVE-2021-45105 and CVE-2021-44832 were found in earlier versions of the log4j library used by the Vertica/Apache Kafka integration. The library has been updated to resolve this issue. |
9.2.1-27
Release Date: 12/23/2021
| Issue Key | Component | Description |
|---|---|---|
| VER-80120 | Kafka Integration | This release updates the Kafka integration’s Log4j library. The updated library addresses the CVE-2021-44228 and CVE-2021-45046 security vulnerabilities found in earlier versions. |
9.2.1-26
Updated: 04/13/21
This hotfix was internal to Vertica.
9.2.1-25
Release Date: 4/13/2021
| Issue Key | Component | Description |
|---|---|---|
| VER-76255 | Data Export | Parquet files exported by Vertica now properly display date values when imported to Impala. |
| VER-76480 | Execution Engine | With Vertica running on machines with very high core counts, complex memory-intensive queries featuring an analytical function that fed into a merge operation sometimes caused a crash if the query ran in a resource pool where EXECUTIONPARALLELISM was set to a high value. This issue has been resolved. |
| VER-76791 | Kafka Integration, Security | An SSL handshake error no longer occurs when Kafka ingests avro data that connects to Vertica using a schema registry URL. |
9.2.1-24
Release Date: 3/16/2021
| Issue Key | Component | Description |
|---|---|---|
| VER-75249 | Security | Previously, CREATE OR REPLACE VIEW could only replace an existing view if the current user was the existing view's owner. Now, DROP privilege is sufficient to replace the view (in addition to CREATE on the SCHEMA, as before). |
| VER-75790 | Kafka Integration | Data ingested through Kafka during a timezone change could result in duplicate records. This issue has been resolved. |
| VER-75942 | Tuple Mover | The Tuple Mover logged a large number of PURGE requests on a projection while another MERGEOUT job was running on the same projection. This issue has been resolved. |
| VER-76127 | Monitoring | The output of get_expected_recovery_epoch is no longer truncated in clusters with more than 20 nodes. |
9.2.1-23
Release Date: 2/2/2021
| Issue Key | Component | Description |
|---|---|---|
| VER-74964 | Storage and Access Layer | Under certain conditions, Vertica could fail while cancelling an INSERT or COPY transaction on EON. This issue has been corrected. |
| VER-75014 | Tuple Mover | Enabling both mergeout caching (deprecated) and reflexive mergeout adversely affected performance on a new or restarted database. This issue has been resolved: when reflexive mergeout is enabled, mergeout caching is automatically disabled. |
| VER-75535 | Optimizer | Analytic functions triggered an Optimizer error when used with a LIMIT OVER clause. This issue has been resolved. |
| VER-75641 | Optimizer | Queries with subqueries on tables with TopK projections sometimes returned with an error. The issue has been resolved. |
9.2.1-22
Release Date: 11/24/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-75095 | Execution Engine | Enabling inter-node encryption adversely affected query performance across a variety of workloads. In many cases, this issue has been addressed with improved performance. |
9.2.1-21
Release Date: 11/6/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-74170 | Data Load / COPY | Added support guidance parameter 'UDLMaxDataBufferSize' with default value 256 x 1024 x 1024 (256 MB). Its value can be increased to avoid 'insufficient memory' errors during User Define Load. |
| VER-74650 | UI - Management Console | If there are multiple IP addresses available on a Vertica cluster, Vertica now prioritizes reachable IP host addresses when trying JDBC connections to the database. |
| VER-74715 | UI - Management Console | If multiple IP addresses are available on a Vertica cluster host, Vertica now confirms that the Agent IP address is reachable and is on a reachable subnet from the MC host. |
| VER-74779 | Optimizer | In some cases, the optimizer required an unusual amount of time to generate plans for queries on tables with complex live aggregate projections. This issue has been resolved. |
9.2.1-20
Release Date: 9/9/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-73876 | Backup/DR | The vbr backup tool now confirms that the Vertica session containing the database snapshot is running throughout the duration of a backup task. |
| VER-74004 | Execution Engine | The query_profiles table now reports the correct number of rows processed when querying an external table stored in parquet files on HDFS. |
9.2.1-19
Release Date: 8/5/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-72841 | Catalog Engine, Execution Engine | Dropping a column no longer corrupts partition-level statistics, causing subsequent runs of the ANALYZE_STATISTICS_PARTITION meta-function on the same partition range to fail. If you have existing corrupted partition-level statistics, drop the statistics and run ANALYZE_STATISTICS_PARTITION to recreate them. |
| VER-73174 | Hadoop | Previously, when accessing data on hdfs Vertica would sometimes connect to the wrong hdfs cluster in cases when several namenodes from different clusters have the same hostname. This is now fixed. |
| VER-73264 | Execution Engine | In some cases, cancelling a query caused subsequent queries in the same transaction to return with an error that they also had been cancelled. This issue has been resolved. |
| VER-73485 | Tuple Mover |
A ROS of inactive partitions was excluded from mergeout if it was very large in relation to the size of other ROS's to be merged. Now, a large ROS container of inactive partitions is merged with smaller ROS containers when the following conditions are true:
|
| VER-73486 | Data Load / COPY | Under certain circumstances, the FJsonParser rejecting rows could cause the database to panic. This issue has been fixed. |
9.2.1-18
Release Date: 7/8/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-72949 | Backup/DR | Vertica backups were failing to delete old restore points when the number of backup objects exceeded 10,000 objects. This issue has been fixed. |
| VER-72969 | Backup/DR | Vertica no longer fails if an object is being restored at the same time that an object is being created and the objects share the same name in different character cases. |
| VER-72999 | Cloud - Amazon, Security | Vertica instances can now only access the S3 bucket that the user specified for communal storage. |
| VER-73075 | Kafka Integration | KafkaExport can now run in fenced mode when SSL is enabled. |
| VER-73109 | Kafka Integration | Previously, the version of the kafkacat utility distributed with Vertica had an issue that prevented it from working when TLS/SSL encryption was enabled. This issue has been corrected, and the version of kafkacat bundled with Vertica can now make TLS/SSL encrypted connections. |
9.2.1-17
Release Date: 6/22/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-72906 | Data Load / COPY, SDK | The protocol used to run a user-defined parser in fenced mode had a bug which would occasionally cause the parser to process the same data multiple times. This issue has been fixed. |
| VER-72971 | Kafka Integration, Security | Previously only one CA certificate was loaded from the kafka_SSL_CA parameter. Now all CA certificates are loaded as trusted CAs. |
| VER-72972 | Kafka Integration | When omitting a CA alias setting up the scheduler's TLS configuration (parameter --ssl-ca-alias), the scheduler loads all certificates into the trust store. When given an alias the scheduler still loads only that alias. |
9.2.1-16
Release Date: 6/15/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-72906 | Data Load / COPY, SDK | The protocol used to run a user-defined parser in fenced mode had a bug which would occasionally cause the parser to process the same data multiple times. This issue has been fixed. |
| VER-72971 | Kafka Integration, Security | Previously only one CA certificate was loaded from the kafka_SSL_CA parameter. Now all CA certificates are loaded as trusted CAs. |
| VER-72972 | Kafka Integration | When omitting a CA alias setting up the scheduler's TLS configuration (parameter --ssl-ca-alias), the scheduler loads all certificates into the trust store. When given an alias the scheduler still loads only that alias. |
9.2.1-15
Release Date: 5/13/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-70708 | UI - Management Console | A problem occurred when an MC Admin user chose to bind to LDAP anonymously, where the setting did not take effect despite clicking 'Apply' and 'Done'. This problem has now been fixed. |
| VER-72347 | Optimizer | Queries with a mix of single-table predicates and expressions over several EXISTS queries in their WHERE clause sometimes returned incorrect results. The issue has been fixed. |
| VER-72421 | Hadoop | On some HDFS distributions, if a datanode is killed during a Vertica query to HDFS, the namenode fails to respond for a long time causing Vertica to time out and roll back the transaction. In such cases Vertica used to log a confusing error message, and if the timeout happened during the SASL handshaking process, Vertica would hang without the possibility of being canceled. Now we log a better error message (saying that dfs.client.socket-timeout value should be increased on the HDFS cluster), and the hang during SASL handshaking is now cancelable. |
9.2.1-14
Release Date: 4/22/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-72111 | DDL - Table | If a column had a constraint and its name contained ASCII and non-ASCII characters, attempts to insert values into this column sometimes caused the database to fail. This issue has been resolved. |
| VER-72114 | Data Removal - Delete, Purge, Partitioning | Vertica now provides clearer messages when drop_partitions fails due to an insufficient resource pool. |
| VER-72116 | Hadoop | Previously, Vertica queries accessing HDFS would fail immediately if an HDFS operation returned 403 error code (such as Server too busy). Vertica now retries the operation. |
| VER-72118 | Optimizer, Recovery | Projection data now remains consistent following a MERGE during node recovery in Enterprise mode |
| VER-72256 | Execution Engine | In some cases, malformed queries on specific columns, such as constraint definitions with unrecognized values or tranformations with improper formats, caused the database to fail. This problem has been resolved. |
9.2.1-13
Release Date: 4/8/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-70461 | AP-Advanced | Queries using user-defined aggregates or the ACD library would occasionally return an error "DataArea overflow". This issue has been fixed. |
| VER-71623 | Backup/DR | Vbr no longer includes the dbadmin password in logging files when the debug level is set to 3 and the dbadmin password is stored in a password file. |
| VER-72069 | Execution Engine | Loading Kafka messages larger than 5MB no longer causes an insufficient memory error. |
9.2.1-12
Release Date: 2/26/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-71087 | Security, Third Party Tools Integration | NULL input to VoltageSecureProtect and VoltageSecureAccess now returns NULL value. |
| VER-70963 | Third Party Tools Integration | Previously, the length of the returned object was based on the input's length. However, numeric formats do not generally preserve size, since 1 may encrypt to 1000000, and so on. This leads to problems such as copying a 20 byte object into a 4 byte VString object. This fix ensures that the length of the output buffer is at least the size of the input length + 100 bytes. |
9.2.1-11
Release Date: 1/31/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-70086 | Backup/DR | If a user deleted an object during a backup on EON mode, the backup could potentially fail. This issue has been resolved. |
| VER-70149 | Client Drivers - VSQL | Previously, the VSQL options -B (connection backup server/port) and -k/-K (Kerberos service and host name) were incompatible, and the latter would be ignored. Now, these options can be set together. |
| VER-70236 | Data Removal - Delete, Purge, Partitioning |
DROP_PARTITIONS requires that the range of partition keys to drop exclusively occupy the same ROS container. If the target ROS container contains partition keys that are outside the specified range of partition keys, the force-split argument must be set to true, otherwise the function returns with an error. In rare cases, DROP_PARTITIONS executes at the same time as a mergeout operation on the same ROS container. When this happens, the function cannot execute the force-split operation and returns with an error. This error message has been modified to better identify the source of the problem, and also provides a hint to try calling DROP_PARTITIONS again. |
| VER-70704 | Optimizer - Statistics and Histogram | ANALYZE_ROW_COUNT can no longer change STATISTICS_TYPE from FULL to ROWCOUNT. |
9.2.1-10
Release Date: 1/13/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-69658 | Backup/DR | Vertica now supports replication from version 9.2SP1-10 to version 9.3 and later. |
| VER-70673 | Data Load / Copy | Sending excessively long inputs to a NUMERIC column in a COPY statement could cause Vertica to fail. This issue has been fixed. |
9.2.1-9
Release Date: 11/20/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-68935 | Cloud - Amazon | The verticad script restarts the vertica process on a node when the operating system starts. On Amazon Linux, the script sometimes was unable to detect the operating system and returned an error. This issue has been resolved. |
| VER-69321 | UDX | GRANT and REVOKE statements now support ALTER and DROP privileges for user-defined functions. |
| VER-69642 | Kafka Integration | Vertica no longer fails when it encounters improper Kafka SSL key/certificate setup error information on RedHat Linux. |
| VER-69667 | Backup/DR | If a copycluster task and a swap partition task ran concurrently, the data that participated in the swap partition could end up missing on the target cluster. This issue has been resolved. |
| VER-69672 | LocalPlanner | Vertica occasionally failed when running COUNT DISTINCT queries with predicates on lead columns in the projection sort order. This issue has been resolved. |
| VER-69674 | Monitoring | In earlier releases, users could set configuration parameter SaveDCEEProfileThresholdUS to a value greater than its maximum range (2^31-1), which led to integer overflow. Vertica now returns an error if the input value is greater than 2^31-1. |
| VER-69784 | Execution Engine | In cases where COUNT (DISTINCT) and aggregates such as AVG were involved in a query of a numeric datatype input, the GroupGeneratorHashing Step was causing a memory conflict when the size of the input datatype (numeric) was greater than the size of output datatype (float for average), producing incorrect results. This issue has been fixed. |
9.2.1-8
Release Date: 10/31/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-67898 | Tuple Mover | Previously, the mergeout thread dedicated to processing active partition jobs ignored eligible jobs in the mergeout queue, if a non-eligible job was at the top of the queue. This issue has been resolved: now the thread scans the entire queue for eligible mergeout jobs. |
| VER-68936 | UI - Management Console | MC catches Vertica’s SNMP traps and generates an alert for each one. MC was not generating an alert for the Vertica SNMP trap: CRC Mismatch. This issue has been fixed. |
| VER-69389 | SAL | Queries could fail when Vertica 9.2 tried to read a ROS file format from Vertica 6.0 or earlier. Vertica now properly handles files created in this format. |
| VER-69354 | Tuple Mover | The algorithm for prioritizing mergeout requests sometimes overlooked slow-loading jobs, especially when these competed with faster jobs that loaded directly into ROS. This could cause mergeout requests to queue indefinitely, leading to ROS pushback. This problem was resolved by changing the algorithm for prioritizing mergeout requests. |
| VER-69398 | Security | When the only privileges on a view came via ownership and schema-inherited privileges instead of GRANT statements, queries on the view by non-owners bypassed the privilege check for the view owner on the anchor relation(s). Queries by non-owners with inherited privileges on a view now correctly ensure that the view owner has SELECT WITH GRANT OPTION on the anchor relation(s). |
| VER-69144 | Security | Before release 9.1, the default Linux file system permissions on scripts generated by the Database Designer were 666 (rw-rw-rw-). Beginning with release 9.1, default permissions changed to 600 (rw-------). This hotfix release reverts default permissions to 666 (rw-rw-rw). |
9.2.1-7
Release Date: 10/3/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-68932 | UI - Management Console | When using AWS, if the user manually upgraded both MC and the Vertica server, and then tried to add an instance to a cluster, a version mismatch error would occur. This problem has been fixed. |
| VER-68863 | Optimizer | Queries sorting on subquery outputs sometimes produced inconsistent results. This issue has been fixed. |
| VER-69228 | Execution Engine | In some cases, queries failed to sort UUIDs correctly if the ORDER BY clause did not specify the UUID column first. This problem has been resolved. |
| VER-68864 | UI - Management Console | When the user configured Extended Monitoring, MC did not properly handle user names that included special characters. This issue has been resolved. |
9.2.1-6
Release Date: 9/12/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-68707 | Data Export, Hadoop | Date Columns now includes the Parquet Logical type, enabling other tools to recognize this column as a Date type. |
| VER-68706 | Data Export | EXPORT TO PARQUET now supports zh_CN.utf8 and ja_JP.utf8. |
| VER-68703 | UI - Management Console | Certain design steps in the Events history tab of the MC Design page were appearing in the wrong order and with incorrect time stamps. This issue has been fixed. |
| VER-68575 | UI - Management Console | MC was failing to add tables to a design when table contained Japanese characters. This issue has been fixed. |
| VER-68574 | Tuple Mover | For partitioned tables, PURGE would not be executed on storage containers without valid partition keys. Reflexive Mergeout generated PURGE requests without checking valid partition keys. As a result, Reflexive Mergeout repeatedly generated PURGE requests for storage containers with invalid partition keys. Reflexive Mergeout no longer generates PURGE request without valid partition keys for storage containers. |
9.2.1-5
Release Date: 8/18/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-68429 | License | Upgrading 8.1.1-x databases with Autopass license installed to 9.0 or later could lead to license tampering startup issues. This problem has been fixed. |
| VER-68497 | Nimbus, Optimizer | Queries with multiple analytic functions over complex expression arguments and different PARTITION BY/ORDER BY column sets would sometimes produce incorrect and inconsistent results between Enterprise and EON. This issue has been fixed. |
| VER-68498 | Catalog Engine | Exporting a catalog on a view that references itself could cause Vertica to fail. This issue has been resolved. |
9.2.1-4
Release Date: 7/31/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-68236 | Optimizer | Prepared statements do not support WITH clause materialization. Previously, Vertica threw an error when it tried to materialize a WITH clause for prepared statement queries. Now, Vertica throws a warning and processes the WITH clause without materializing it. |
| VER-68156 | Optimizer | Certain combinations of analytic functions applied to the output of a merge join would occasionally cause Vertica to crash. This issue has been fixed. |
| VER-68136 | Tuple Mover | TM_MOVESTORAGE ran in an infinite loop if the default storage location was labeled and a non-data usage storage location was unlabeled. This issue has been resolved: now, ROS containers are never moved to a non-data usage storage location |
| VER-68111 | QA | When a query returned many rows with wide columns, Vertica threw the following error message: "ERROR 8617: Request size too big." This message incorrectly suggested that query output consumed excessive memory. This issue has been fixed. |
| VER-68078 | Nimbus | In the past, DDL transactions remained open until all pending file deletions were complete. In Eon mode, this dependency could cause significant delays. This issue has been resolved: now, DDL transactions can complete while file deletions continue to execute in the background. |
| VER-68225 | Data load / COPY | A bug in the Apache Parquet C++ library sometimes caused Vertica to fail when reading Parquet files with large Varchar statistics. This issue has been fixed. |
9.2.1-3
Release Date: 7/2/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-67872 | Catalog Engine | Previously, if a DROP statement on an object failed and was rolled back, Vertica would generate a NOTICE for each dependent object. This was problematic in cases where the DROP operation had a large number of dependencies. This issue has been resolved: Vertica now generates up to 10 messages for dependent objects, and then displays the total number of dependencies. |
| VER-67938 | Data load / COPY | Vertica could fail if its client disconnected during a COPY LOCAL with REJECTED DATA. This issue has been fixed. |
9.2.1-2
Release Date: 6/17/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-67632 | Execution Engine | Some queries with complex predicates ignored cancel attempts, manual or via the runtime cap, and continued to run for a long time. Cancel attempts themselves also caused the query to run longer than it would have otherwise. This issue has been fixed. |
| VER-67593 | Client Drivers - ODBC, Data Removal - Delete, Purge, Partitioning | Queries use the query epoch (current epoch -1) to determine which storage containers to use. A query epoch is set when the query is launched, and is compared with storage container epochs during the local planning stage. Occasionally, a swap partition operation was committed in the interval between query launch and local planning. In this case, the epoch of the post-commit storage containers was higher than the query epoch, so the query could not use them, and it returned empty results. This problem was resolved by making SWAP_PARTITIONS_BETWEEN_TABLES atomic. |
9.2.1-1
Release Date: 5/23/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-67038 | Build and Release | A new error message in Export To Parquet did not have an error code. This issue has been fixed. |
| VER-67339 | Backup/DR | Dropping the user that owns an object involved in a replicate or restore operation during that replicate or restore operation no longer causes the nodes involved in the operation to fail. |
| VER-67362 | Data Export, Hadoop | Dictionary size is now accounted for when estimating row group sizes during data export to parquet format. As a result row groups can no longer exceed their specified size. |
| VER-67400 | UDX | Flex table views now properly show UTF-8 encoded multi-byte characters. |
| VER-67408 | Client Drivers - Installation Package | Incorrect permissions on ODBC driver message files potentially prevented the driver from retrieving error messages in some situations, such as the user not belonging to the same group as the message files' owner. This problem has been corrected. |
| VER-67409 | DDL - Table | The database statistics tool SELECT ANALYZE_STATISTICS no longer acquires a GCL-X lock when running against local temp tables. |
| VER-67410 | Optimizer | Vertica now supports subqueries in the ON clause of a query. |
| VER-67411 | Execution Engine | On rare occasions, a query that exceeded its runtime cap automatically restarted instead of reporting the timeout error. This issue has been fixed. |
| VER-67412 | Installation Program | If a standby node had been replaced in past with failed nodes with deprecated projections, the identify_unsupported_projections.sh script could not reflect on the standby node. When upgrading to 9.1 or later, the standby might may not start due to failure of the 'U_DeprecateNonIdenticallySortedBuddies' and/or 'U_DeprecatePrejoinRangeSegProjs' task. This issue has been resolved. |
| VER-67414 | Optimizer | Queries that perform an inner join and group the results now return consistent results. |
| VER-67425 | Hadoop | Vertica can now read tinyint values in parquet files generated by Apache Spark. |
| VER-67459 | Execution Engine | The run_index_tool meta-function can now be cancelled. Together with projection name filtering and using multiple threads, dbadmins should be less reluctant to run this potentially long-running tool. |
9.2.1-0
Release Date: 5/8/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-36308 | UI - Management Console | The Vertica MC linux service : /etc/init.d/vertica-consoled status would always display status OK without showing the actual MC state (Running or Stopped). This issue has been resolved. |
| VER-36987 | Optimizer - Statistics and Histogram | If DROP_STATISTICS specified a table and the argument HISTOGRAMS, the function dropped all statistics for the table, including row count. This issue has been resolved: the function now drops only the histograms for that table. |
| VER-38419 | Optimizer - GrpBy and Pre Pushdown | Aggregate functions can now be pushed down into UNION-ALL subqueries, if it is safe to do so. |
| VER-43373 | DDL - Table | CREATE TABLE LIKE...INCLUDING PROJECTIONS generated projections for the cloned table that aliased the new anchor table table with the name of the original anchor table. Projections for tables that are created with CREATE TABLE LIKE no longer use this aliasing mechanism. |
| VER-55257 | Client Drivers - ODBC | Issuing a query which returns a large result set and closing the statement before retrieving all of its rows can result in the following error when attempting subsequent operations with the statement: "An error occurred during query preparation: Multiple commands cannot be active on the same connection. Consider increasing ResultBufferSize or fetching all results before initiating another command." |
| VER-56790 | Client Drivers - JDBC, Client Drivers - ODBC | Previously, certain server errors were not correctly propagated to the application, which resulted in the correct native error code and the original server error message not being seen by the application when it called SQLGetDiagRec(). This problem has been corrected. |
| VER-58419 | UI - Management Console | 'Export Design' button wasn't getting enabled after design was completed. This issue has been fixed. |
| VER-59114 | Client Drivers - VSQL | Sometimes vsql was not able to locate a Kerberos Key Distribution Center (KDC) that was identified only via specially-named DNS records. This issue has been been fixed. |
| VER-62414 | Hadoop | Previously, Vertica sometimes generated Parquet files with too many rowgroups in a file. Loading such files using external Parquet tools caused a performance degradation or out of memory errors. This has been fixed. |
| VER-63297 | Client Drivers - ADO | Previously, if an integer column value was split across multiple reads by the ADO.NET driver, it was not correctly captured. This has been corrected. |
| VER-63389 | Data Export, Hadoop | Previously, Vertica sometimes generated Parquet files with too many rowgroups in a file. Loading such files using Vertica caused a performance degradation. This has been fixed. |
| VER-63769 | Data Export, Error Handling, Hadoop | Previously, Parquet and ORC external tables would throw an error if the load path contained an empty folder. A new parser option 'allow_no_match' when set to 'true' now returns an empty result set instead of an error. |
| VER-64592 | DDL - Table | Vertica was unable to add a foreign key constraint to a table if the table was referenced by a key in another table that used the same constraint name. Now, Vertica checks for constraint name conflicts only within the same table. |
| VER-64912 | Backup/DR | Altering the owner of a replicated schema with the CASCADE clause caused a node crash on the target database. This issue has been fixed. |
| VER-64941 | DDL - Table | Previously, ALTER TABLE...ADD COLUMN required you to explicitly list all existing projections that you wished to update with the new column. You can now update all projections by qualifying ADD COLUMN with the new option ALL PROJECTIONS. |
| VER-65065 | Kafka Integration | Vertica now properly supports TLS certificate chains for use with Kafka Scheduler and UDx. |
| VER-65082 | Execution Engine | Under certain workloads, glibc can accumulate a significant amount of free memory in its allocation arenas, free memory that nevertheless consumes physical memory as indicated by RSS usage. Vertica now detects and automatically consolidates and returns much of that free memory back to the operating system. |
| VER-65137 | Data load / COPY | Rejected data and exceptions files during a COPY statement are created with file permissions 666. |
| VER-65154 | License | Due to a miscalculation, the license auditor running in sampling mode showed an incorrectly large standard error. The standard error is the number that appears after the +/- sign on the data size line in license compliance messages. This issue has been fixed. |
| VER-65249 | UI - Management Console | In the MC, the license page would periodically not show all the licenses that the database may contain. This issue has now been resolved. |
| VER-65257 | Hadoop | Export to Parquet previously crashed when the export included a combination of Select statements. This issue has been fixed. |
| VER-65333 | Nimbus Subscriptions | After upgrading to 9.2, the Eon database crashed after running rebalance_shards. This issue has been fixed. |
| VER-65338 | UI - Management Console | The MC license page would periodically not show the graph representing the license usage. This issue has now been fixed. |
| VER-65419 | Security | Setting a row-based access policy on an underlying table of a view denied the user access to the view. This issue is fixed so the user can see the view as intended. |
| VER-65484 | Backup/DR | Removed the redundant "Missing info files: skipping..." warnings in the vbr log when performing backup tasks. |
| VER-65501 | Backup/DR | Running the remove task using a vbr config file with an incorrect "snapshotName" removed entries from the backup manifest file. This problem has been resolved. |
| VER-65604 | Security | Passwords with a semicolon are no longer printed in the log. |
| VER-65718 | Tuple Mover | If you upgraded a database to version 9.2.0 from any earlier release and configuration parameter MergeoutCache was set to 1 (enabled), the upgraded database was unable to start. Now, if MergeoutCache is set to 1 in the earlier release, the upgraded database ignores this setting. To enable MergeoutCache, you must also set EnableReflexiveMergeout to 0 (disabled). |
| VER-65776 | UI - Management Console | While logged into the MC as a non-admin user, the table in the Load page's "Continuous tab" would periodically not show all the current running Vertica schedulers that are in use. This issue has been resolved. |
| VER-65801 | Catalog Engine, Subscriptions | Database started with missing shards. This issue is now resolved. |
| VER-65818 | Client Drivers - ADO | The way the ADO.NET driver previously tracked statements associated with a connection to ensure that they were always closed when the connection was closed created a memory leak in some use cases. This problem has been corrected. |
| VER-65866 | Execution Engine, Nimbus, S3 | On rare occasions, a bug in S3 streaming read caused fatal errors. This issue has been resolved. |
| VER-66058 | DDL | In Eon mode with DFS, if a node was down, queries was liable to fail and return the error "System is not k-safe ..." This issue has been resolved. |
| VER-66080 | Execution Engine | Long 'like' patterns with many non-ASCII characters such as Cyrillic were liable to crash the server. This issue has been resolved. |
| VER-66088 | Scrutinize | The scrutinize command previously used the /tmp directory to store files during collection. It now uses the specified temp directory. |
| VER-66095 | Data load / COPY | The FJsonParser no longer fails when loading JSON records with more than 4KB of keys and the option reject_on_duplicate_key=true. |
| VER-66136 | UI - Management Console | Running the 'Explain" query option for an unsegmented projection on the MC Query Plan page could trigger the error: "There is no metadata available for this projection". This issue has been resolved. |
| VER-66228 | Optimizer | Vertica now disables fast const loading if you are using hierarchical partitioning. |
| VER-66240 | Optimizer - Statistics and Histogram | The database statistics tool SELECT ANALYZE_STATISTICS no longer fails if you call it when the cluster is in a critical state. |
| VER-66308 | Hadoop | Previously, NULLs in text struct data when loaded through the HCatalog Connector produced a null pointer exception. This has been fixed. |
| VER-66327 | Client Drivers - JDBC, Security | JDBC could fail with a stack overflow error when receiving more than 512 MB of data from Vertica. This issue was due to an incompatibility between Java's and OpenSSL's implementations of TLS renegotiation. Vertica now contains the tls_renegotiation_limit parameter. You can set this parameter to 0 to disable SSL/TLS renegotiation and avoid the issue. |
| VER-66345 | Data load / COPY | Vertica's Parquet file parser would occasionally incorrectly reject rows from files containing a column with a max definition level of zero and one or more columns with a nonzero max definition. This issue has been fixed. |
| VER-66489 | Optimizer | During an optimized merge, Vertica tried to plan the DELETE portion of the MERGE query twice, sometimes triggering an error. This issue has been resolved. |
| VER-66589 | Execution Engine | Partition pruning did not work when querying a table's TIMESTAMP column, where the query predicate specified a TIMESTAMPTZ constant. This issue has been resolved. |
| VER-67056 | Admin Tools | Sometimes during database revive, admintools treated s3 and hdfs user storage locations as local filesystem paths. This led to errors during revive. This issue has been resolved. |
9.2.0-8
Release Date: 1/27/2020
| Issue Key | Component | Description |
|---|---|---|
| VER-70856 | LocalPlanner | Vertica occassionally failed when running COUNT DISTINCT queries with predicates on lead columns in the projection sort order. This issue has been resolved. |
9.2.0-7
Release Date: 4/11/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-66705 | Data Load / Copy | The FJsonParser no longer fails when loading JSON records with more than 4KB of keys and the option reject_on_duplicate_key=true. |
| VER-66730 | UI - Management Console | Running the 'Explain" query option for an unsegmented projection on the MC Query Plan page could trigger the error: "There is no metadata available for this projection". This issue has been resolved. |
| VER-66742 | UI - Management Console | The MC would not properly display the license chart on the license tab when license usage exceeded 10TB. This issue has been resolved. |
| VER-66750 | Kafka Integration | Vertica now properly supports TLS certificate chains for use with Kafka Scheduler and UDx. |
| VER-66765 | Hadoop | Export to Parquet previously crashed when the export included a combination of Select statements. This issue has been fixed. |
| VER-66808 | Backup/DR | Altering the owner of a replicated schema with the CASCADE clause caused a node crash on the target database. This issue has been fixed. |
| VER-66810 | Optimizer Statistics and Histogram | The database statistics tool SELECT ANALYZE_STATISTICS no longer fails if you call it when the cluster is in a critical state. |
| VER-66838 | Optimizer | Vertica now disables fast const loading if you are using hierarchical partitioning. |
| VER-66839 | Client Drivers - JDBC, Security | JDBC could fail with a stack overflow error when receiving more than 512 MB of data from Vertica. This issue was due to an incompatibility between Java's and OpenSSL's implementations of TLS renegotiation. Vertica now contains the tls_renegotiation_limit parameter. You can set this parameter to 0 to disable SSL/TLS renegotiation and avoid the issue. |
| VER-66856 | Optimizer | During an optimized merge, Vertica would attempt to perform planning of DELETE portion of the MERGE query twice, sometimes triggering an error. This issue has been resolved. |
9.2.0-6
Release Date: 3/21/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-66271 | Scrutinize | The scrutinize command previously used the /tmp directory to store files during collection. It now uses the specified temp directory. |
| VER-66411 | S3 | Eon mode contained an unnecessary check for files on communal storage before removing those files. That check could slow the delete operation and increase request costs. The check has been removed. |
| VER-66498 | Data load / COPY | Rejected data and exceptions files during a COPY statement are now created with file permissions 666. |
| VER-66526 | DDL |
In Eon mode with DFS, if a node was down, queries could fail with the error "System is not k-safe ..." This issue has been fixed. |
| VER-66527 | Execution Engine | Some long 'like' patterns with many non-ASCII characters could cause Vertica to fail. This issue has been fixed. |
9.2.0-5
Release Date: 3/5/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-66420 | Data load / COPY | Parquet files containing columns with a maximum definition level of zero could have rows erroneously rejected during an external table query or COPY statement. This issue has been fixed. |
9.2.0-4
Release Date: 2/14/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-66009 | Execution Engine, Nimbus, S3 | There was a bug in S3 streaming read that, in rare occasions, lead to fatal errors. This issue has been fixed. |
| VER-65851 | Security | Setting a row-based access policy on an underlying table of a view denies the user access to the view. This issue is fixed. |
9.2.0-3
Release Date: 1/29/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-65822 | Data load / COPY | Occasionally, an empty response from S3 (response code 0) could cause some database operations to fail. This issue has been fixed. |
| VER-65772 | UI - Management Console | Due to a miscalculation, license auditor running in sampling mode showed a much larger standard error than it actually was (this is the number you see after the +/- sign on the data size line in license compliance messages). This issue has been fixed. |
| VER-65767 and VER-65765 | Execution Engine | In Eon mode, the number of List requests made to S3 when querying out-of-depot ROS files has been reduced. |
| VER-65736 | Backup/DR | Running the remove task using a vbr config file with an incorrect "snapshotName" removed entries from the backup manifest file. This problem has been resolved. |
| VER-65556 | UI - Management Console | License usage was showing 0% when Autopass license is used. This issue has been fixed. Vertica server hotfix upgrade is also required for this fix to take effect (same release number). |
9.2.0-2
Release Date: 1/3/2019
| Issue Key | Component | Description |
|---|---|---|
| VER-65444 | UI - Management Console | Management Console on AWS did not display the AMI version which may have caused user confusion if the MC was not hotfixed on a Vertica hotfix AMI. This issue has been fixed. |
| VER-65395 | UI - Management Console | When the Management Console on premises attempted to download the Vertica AMI repository file, an error occurred. The error did not cause any functionality failures since the repository file is not used for MC on premises. This issue has been fixed. |
9.2.0-1
Release Date: 12/12/2018
| Issue Key | Component | Description |
|---|---|---|
| VER-65348 | DDL - Table | When copying a table using the CREATE TABLE LIKE command, all column default expressions were lost if one of the columns has a default value of a sequence. Otherwise, default expressions were copied to the new table. This issue has been fixed. |
| VER-65407 | Eon, Subscriptions | After upgrading to 9.2, the Eon database crashed after running rebalance_shards. This issue has been fixed. |
9.2.0-0
Release Date: 11/27/2018
| Issue Key | Component | Description |
|---|---|---|
| VER-63430 | Optimizer |
At times, query performance was sub-optimal when both the following occurred:
This issue been fixed. |
| VER-62662 | Data load / COPY | Occasionally, a COPY or external table query could crash a node. This issue has been fixed. |
| VER-48026 | DDL - Table | If you moved a table with foreign keys to a new schema, attempts to drop the original schema without CASCADE returned a rollback error that referenced a foreign key dependency. This issue has been fixed. |
| VER-62002 | DDL - Table |
Vertica placed an exclusive lock on the global catalog while it created a query plan for CREATE
TABLE AS |
| VER-59212 | Sessions | In cases where a user had privileges on a user resource pool but not the GENERAL pool, certain DDL statements would fail. This issue has been fixed. |
| VER-63405 | Catalog Engine, Spread | If a control node and one of its child nodes went down, attempts to restart the second (child) node sometimes failed. This issue has been fixed. |
| VER-63839 | Data load / COPY |
The SKIP keyword of a COPY statement was not properly supported with the FIXEDWIDTH data format. This issue has been fixed. |
| VER-62810 | Data load / COPY | In a COPY statement, excessively long invalid inputs to any date or time columns could cause stack overflows, resulting in a crash. This issue has been fixed. |
| VER-64716 | Data load / COPY, FlexTable | When parsing an array, FJSON PARSER sometimes returned inconsistent results with Vertica versions prior to 9.1SP1. This issue has been fixed. |
| VER-61431 | Optimizer - Plan Stability | The optimizer did not consider active directed queries when it created plans for queries that included a LABEL hint. This issue has been fixed. |
| VER-60716 | FlexTable | The MAPITEMS function returned truncated map values. The issue has been fixed. |
| VER-63650 | DDL | In some cases, attempts to add a column with a NOT NULL constraint partially failed: Vertica added the column but omitted the constraint. This issue has been fixed. |
| VER-63550 | S3 | S3Export was not thread safe when the data contained time/date values. Therefore, you could not use S3Export with PARTITION BEST when exporting time/date values. This issue has been fixed. |
| VER-64421 | Cloud - Amazon, UI - Management Console | At times, Management Console failed to add a new host to the database after a long wait. This issue has been fixed. |
| VER-61289 | Execution Engine, Hadoop | If a Parquet file metadata was very large, Vertica consumed more memory than was reserved and crashed when the system ran out of memory. This issue has been fixed. |
| VER-63742 | AMI, UI - Management Console | Management Console deployed a Vertica CloudFormation Template in an existing VPN/subnet failed to provision and revive the Vertica database with the user providing a VPN access CIDR. This issue has been fixed. |
| VER-64645 | UI - Management Console |
SMTP alerts were not being received in the planned timeframe, even during network disconnection. This issue has been fixed. |
| VER-64705 | UI - Management Console | The permissions of /opt/vconsole/mcdb/derby/mcdb/tmp were not being maintained at a secure setting through restarts of the Management Console. This issue has been fixed. |
| VER-61351 | Admin Tools | Adding large numbers of nodes in a single operation could lead to an admintools error about parsing output. This issue has been fixed. |
| VER-60695 | Optimizer | The optimizer could not use a fast plan to perform a refresh operation on tables with multiple live aggregrate projections. Now, the optimizer applies the refresh operation on each live aggregrate projection as a separate transaction, and applies the fast plan to each live aggregrate projection. This significantly reduces the time required to refresh tables with multiple live aggregrate projections. |
| VER-63861 | AP-Advanced | If you ran APPROXIMATE_COUNT_DISTINCT_SYNOPSIS on a database table that contained NULL values, the synopsis object that it returned sometimes was larger than the one it returned after the NULL values were removed. This issue has been fixed. |
| VER-45444 | DDL - Projection | In many cases, Tuple Mover operations were adversely impacted by the high default number of segmentation and sort columns in a superprojection. This issue has been fixed. |
| VER-64112 | Optimizer | Very large expressions could run out of stack and crash the node. This issue has been fixed. |
| VER-51210 | Execution Engine, Optimizer | Removed misleading documentation that suggested ANY and ALL operators can be used to evaluate arrays. Attempts to do so now throw an error. |
| VER-64351 | Tuple Mover | When executing heavy workloads over an extended period of time, the Tuple Mover was liable to accumulate significant memory until its session ended and it released the memory. This issue has been fixed. |
| VER-63844 | DDL - Projection | The catalog stored incorrect information about pinned projections. This issue has been resolved. |
| VER-63841 | Execution Engine |
In some regular expression scalar functions, Vertica would crash for certain long input strings. This issue has been fixed. |
| VER-62988 | Data load / COPY, Hadoop | Queries involving a join of two external tables loading Parquet files sometimes caused Vertica to crash. The crash happened in a very rare situation due to memory misalignment. This issue has been fixed. |
| VER-58472 | UI - Management Console | Management Console could not import multiple clusters when the host had the same private IP address as the private IP address of a previously imported cluster. This issue has been fixed. |
| VER-61741 | Optimizer | When a projection was created with only the PINNED keyword, Vertica incorrectly considered it a segmented projection. This caused optimizer internal errors and incorrect results when loading data into tables with these projections. This issued has been fixed. IMPORTANT: The fix only applies to newly created pinned projections. Existing pinned projections in the catalog are still incorrect and need to be dropped and recreated manually. |
| VER-61351 | Admin Tools | Adding large numbers of nodes in a single operation could lead to an admintools error parsing output. This issue has been fixed. |
| VER-63728 | Catalog Engine | Having frequent CREATE/INSERT/DROP tables caused a memory leak in the catalog. This issue has been fixed. |
| VER-63044 | Optimizer | The MERGE USING and INSERT SELECT operations, which selected data to be inserted or merged via a query with subqueries under Outer Joins, would sometimes result in an Internal Error. This issue has been fixed. |
| VER-62249 | Optimizer | Vertica evaluated permissions on external sources when creating an external table while holding GCLX. Sometimes this caused GCLX to timeout if there were issues with the file system of the external sources. This issue is now fixed. |
| VER-57071 | Optimizer | In a materialized WITH statement, when there are WITH clauses that have the same alias as regular tables in the FROM clause, Vertica sometimes failed to parse the query correctly. This issue has been fixed. |
| VER-64269 | UDX | Queries with CASE-like expressions over inline functions/SQL macros that return strings and that evaluate CASE expressions internally sometimes returned an error such as "Function can't be used with an operator." This issue has been fixed. |
| VER-47310 | Installation Program | Vertica was not installing properly on OpenStack virtual machines. This issue has been fixed. |
| VER-63969 | Front end - Parse & Analyze | When a meta-function was used in a materialized WITH clause, Vertica process could crash with a "VAssert(0)" error. This issue has been fixed. |
| VER-64858 | Optimizer | An historical query (i.e., at epoch) did not fold stable functions into constants properly, which caused significant performance degradation compared to a non-historical query. This issue has been fixed. |
| VER-64378 | Data load / COPY | A COPY statement with AUTO copy mode failed to handle TRICKLE copy mode set as the table loading mode properly, which caused loaded data to fail over to ROS containers when the WOS pool was full. This issue has been fixed. |
| VER-60916 | DDL, Hadoop | Creating a view can be expensive if a view query is complex or references external storage. This is because Vertica plans the view query during view creation, although the plan is only for validation purpose and is dropped after view creation. You can optionally turn off planning by setting DisableViewQueryPlanning to true. |
| VER-60247 | Kafka Integration |
You could not configure the scheduler and add microbatches dynamically when the scheduler was running. This issue has been fixed. |