Resolved issues
Resolved issues release notes for 24.1.x.
24.1.0-4
Updated 04/18/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-91666 | ResourceManager | If the default resource pool, defined by the DefaultResourcePoolForUsers configuration parameter, was set to a value other than 'general', the user's view incorrectly reported the non-general resource pool as the default pool when the user didn't have that non-general pool set in the profile. This issue has been resolved. The default pool in such cases is now correctly reported as 'general'. |
| VER-92112 | Catalog Engine | Previously, syslog notifiers could cause the node to go down when attached to certain DC tables. This issue has been resolved. |
| VER-92286 | Sessions | The ALTER USER statement could not set the idle timeout for a user to the default value, which is defined by the DefaultIdleSessionTimeout configuration parameter. If the empty string was specified, the idle timeout was set to unlimited. This issue has been resolved. You can now set the idle timeout to the DefaultIdleSessionTimeout value by specifying 'default' in the ALTER USER statement. |
| VER-92534 | Data load / COPY | When the Avro parser would read a byte array that is at most 8 bytes long into a numeric-typed target, it would only accept a single-word numeric as the target type. This has been resolved; now, the Avro parser supports reading short byte arrays into multi-word numeric targets. |
| VER-92662 | Scrutinize |
The scrutinize utility produces a tarball of the data it collects. Previously, scrutinize could fail to create this tarball if it encountered a broken symbolic link. This has been fixed, and the size of the tarball is now logged to scrutinize_collection.log. |
| VER-92747 | HTTP | Changing the Vertica server certificate triggers an automatic restart of the built-in HTTPS server. When this happened on a busy system, the nodes could sometimes go down. The issue has been fixed. |
| VER-92819 | Data load / COPY | In COPY, some missing error checks made it so certain invalid input could crash the database. This has been resolved. |
| VER-92926 | Installation Program |
When you installed Vertica on RHEL 9 with the install_vertica script, there was a warning about a missing ] character. This issue has been resolved. |
| VER-93250 | EON, S3 | Previously, FIPS-enabled databases crashed when Vertica accessed an S3 bucket. This issue has been resolved. |
| VER-93325 | Execution Engine | User-Defined Aggregates didn't work with single distinct built-in aggregate in the same query when the input wasn't sorted on grouping columns plus distinct aggregate column. The issue has been resolved. |
| VER-93527 | ComplexTypes, Kafka Integration | Loading JSON/Avro data with Kafka and Flex parsers into tables with many columns suffered from performance degradation. The performance issue has been resolved. |
24.1.0-3
Updated 03/13/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-91789 | Logging | The LogRotate metafunction and timer service now support dbLog files. |
| VER-92164 | Procedural Languages | Previously, running certain types of queries inside a stored procedure could cause the database to go down. This issue has been resolved. |
| VER-92577 | Data load / COPY | Previously Vertica had poor performance when loading wide tables using RecordParser that performs case-insensitive comparisons. This issue has been resolved. |
| VER-92609 | Execution Engine | When you executed a query that filtered data into a JOIN statement, the query processed incorrectly or returned an error. This issue has been resolved. |
24.1.0-2
Updated 02/27/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-91476 | Execution Engine | Since Version 11.1SP1, in some cases, an optimization in the query plan caused queries running under Crunch Scaling mode of COMPUTE_OPTIMIZED to produce wrong results. This issue has been resolved. |
| VER-91713 | Optimizer | Queries with identically looking predicates on different tables used in different subqueries where predicates have very different selectivity could result in bad query plans and worse performance due to incorrect estimates on those tables. The issue has been resolved. |
| VER-91741 | Execution Engine | The NULLIF function would infer its output type based on only the first argument. This led to type compatibility errors when the first argument was a small numeric type and the second argument was a much larger numeric type. This has been resolved; now, numeric NULLIF accounts for the types of both arguments when inferring its output type. |
| VER-91792 | Execution Engine | In rare situations, a logic error in the execution engine "ABuffer" operator would lead to buffer overruns resulting in undefined behavior. This issue has been resolved. |
| VER-91817 | Execution Engine | Vertica's execution engine pre-fetches data from disk to reduce wait time during query execution. Memory for the pre-fetch buffers was not reserved with the resource manager, and in some situations a pre-fetch buffer could grow to a large size and bloat the memory footprint of a query until it completed. Now queries will account for this pre-fetch memory in requests to the resource manager; and several internal changes mitigate the long-term memory footprint of larger-than-average pre-fetch buffers. |
| VER-91909 | Optimizer | When a node goes down in Eon mode, the buddy node that handles double duty did not adjust the resource calculation. Now, the behavior is consistent with the Enterprise mode node-down scenario. |
| VER-91959 | Execution Engine | Queries using WITH clauses which refer to the temporary relation at least N times, where N is the value of the configuration parameter "EnableWITHTempRelReuseLimit", could suddenly abort the entire Vertica process if an exception (such as running out of temp space) occurred while materializing the temporary relation. We have improved the exception handling of this routine to avoid suddenly crashing the entire process, returning a normal error back to the user when possible or at least handling a PANIC in the fall-back scenario. |
| VER-92054 | Procedural Languages | Fixed memory leaks that could occur with certain stored procedures. |
| VER-92108 | DDL - Projection | When we would scan over a projection sorted by two columns (ORDER BY a,b) and materialize only the second one in the sort order (b), we would mistakenly assume the scan is sorted by that column for the purposes of collecting column statistics. This would lead to possible incorrect results when predicate analysis is enabled, and has now been resolved. |
| VER-92123 | Optimizer | Queries using the same views repeatedly would sometimes return errors if those views included WITH clauses. The issue has been resolved. |
24.1.0-1
Updated 01/25/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-91335 | Data Export | Previously, large (chunked) file uploads from Vertica to GCS (such as exports of Parquet to GCS) would fail if the uploaded files included a special character in their path. This issue has been resolved. |
| VER-91549 | Execution Engine | When a hash join on unique keys would spill, the value columns would sometimes have alignment issues between how the hash table was written and how it gets read by the spill code. If these value columns were string types, this could lead to a crash. This issue has been resolved. |
24.1.0-0
Updated 01/09/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-28231 | Data load / COPY |
Copy statement FILLER columns may now have the same name as table columns. Expressions referring to a column which has the same name between the table and the FILLER column set may be fully-qualified to resolve ambiguities with either the table name, or the special
\*FILLER\* relation. |
| VER-80570 | Data Collector | If a notifier was set for some DC tables and then subsequently dropped, it still remained present in those DC table policies. This could cause a very large number of messages in vertica.log and potential node crashes. The issue was resolved by making "DROP NOTIFIER" support the CASCADE logic. Without CASCADE, drop would fail for the notifiers still used by DC tables. |
| VER-85618 | Optimizer | In version 10.1, Vertica updated its execution engine to sample execution times and selectivity of query predicates and join predicates to run them in the most efficient order. This has been disruptive to users who wrote queries which depended on a certain evaluation order, in particular that single-table predicates would be evaluated before join conditions. In particular, queries whose single-table predicates filter out data which would raise a coercion error at the join condition would sometimes raise an error after this change due to the join condition being evaluated first. Now, we improved this experience by ensuring that join conditions do not raise type coercion errors when they are evaluated before single-table predicates. |
| VER-86330 | UI - Management Console | The Vertica CloudFormation Templates (CFTs) available on the Amazon Web Services Marketplace were updated to enhance security. |
| VER-86838 | Execution Engine | In some circumstances, there were long timeouts or the process might hang indefinitely when the KafkaAvroParser accessed the Avro Schema Registry. This issue has been resolved. |
| VER-87863 | Machine Learning | Because of legacy contingencies of the SEEDED_RANDOM function, the function is left as is, and a new DISTRIBUTED_SEEDED_RANDOM function is added that generates a correct distribution of pseudorandom numbers. As with SEEDED_RANDOM, the new function is not publicly documented and supported because it does not meet the general expectations of a seeded random function. |
| VER-88411 | Security | In cases of intermittent network connectivity to an LDAP server, Vertica will now retry bind operations. |
| VER-88467 | Client Drivers - VSQL | When you executed CREATE ROUTING RULE to create a workload routing rule for a subcluster that did not exist, the error message returned an incorrect object ID for the nonexistent subcluster. This issue has been resolved, and now the error message returns the subcluster name provided in the TO SUBCLUSTER clause. |
| VER-88499 | Installation Program, Installation: Server RPM/Deb | The Vertica installer outputs hints with URLs to the Vertica documentation website to help users with the installation process. The URLs in the installer have been updated to reflect a change in the Vertica documentation URL format. |
| VER-88658 | Kafka Integration | When a notifier was set for the NotifierErrors or NotifierStats Data collector (DC) tables, notifications sent with a Kafka notifier might cause a loop that produced an infinite stream of notifications. This might result in severely degradated node performance. This issue has been resolved. Now, notifications are disabled for these DC tables, and any existing notifiers have been removed from these tables. |
| VER-88985 | UI - Management Console |
The HTTP Strict-Transport-Security (HSTS) response header was added to all MC responses. This header informs the browser that you should access the site through HTTPS only, and that the browser should automatically convert any HTTP connections to HTTPS. |
| VER-89103 | Data load / COPY |
If a Parquet query or load were to be interrupted (such as by a LIMIT clause, exception during execution, or user cancellation) while the database has configuration parameter ParquetColumnReaderSize set to zero, then Vertica could crash. This issue has been resolved. |
| VER-89211 | Security |
The following improvements have been made to LDAPLink:
|
| VER-89284 | Tuple Mover | When the node with the lowest OID became secondary (for example, during cluster demotion), there might have been an increased number of deadlocks and timeouts due to Data Manipulation Language (DML) statements and internal Tuple Mover tasks. This issue has been resolved. |
| VER-89369 | EON, Execution Engine | A LIKE ANY or LIKE ALL expression with a non-constant pattern argument on the right-hand side of the expression sometimes resulted in a crash or incorrect internal error. This issue has been resolved. Now, this type of pattern argument results in a normal error. |
| VER-89447 | Optimizer | In some circumstances, a UNION query that grouped an expression that coerced a value to a common data type returned an error. This issue has been resolved. |
| VER-89482 | UI - Management Console | Node.js has been upgraded to address the CVE-2023-32002 and CVE-2022-43548 security vulnerabilities. |
| VER-89508 | Execution Engine | When casting a negative numeric value to an integer and the result of that cast would be 0, then we would incorrectly get an "out of range" error. This has been resolved. |
| VER-89530 | ComplexTypes, Data load / COPY | A logic gap in the source code could lead to an infinite loop while loading complex arrays with thousands of elements, causing the DML statement to never complete. This issue has been resolved. |
| VER-89623 | Data load / COPY | Loading JSON arrays into table columns having different case for JSON key and table column used to fail in some cases. The issue has been fixed. |
| VER-89647 | Hadoop | Previously, 'Get block locations' events were missing from the dc_udfs_events table. This issue has been resolved. |
| VER-89665 | Backup/DR | Backups to S3 object storage and Google Cloud Storage failed and returned a "Temp path" error. This issue has been resolved. |
| VER-89684 | Scrutinize | The parameter --log-limit determines the maximum size of the vertica log that will be preserved when running scrutinize. The limit is applied to the vertica.log file on all nodes in the cluster. The default value changed from 1GB to unlimited. |
| VER-89721 | Security | Previously, when configuring a chain of certificates longer than a root CA certificate and a client certificate for internode TLS, the configuration would successfully be applied, but cause the cluster to shut down. This has been resolved. |
| VER-89825 | Backup/DR | On HDFS, vbr tried to delete storage files from the wrong fan-out directory. This has been resolved by providing vbr with the correct fan out directory. |
| VER-89874 | Catalog Engine |
During load planning, the EnableWithTempRelReuseLimit configuration parameter was temporarily set to 1. This affected other sessions on the same node, and concurrent COPY commands might make this change permanent. This issue has been resolved. |
| VER-89881 | Catalog Engine | ALTER SESSION no longer crashes the node when a user without USAGE privileges on the public schema sets a non-udparameter. |
| VER-89933 | Catalog Engine | Queries now run correctly when the files of delete vectors are in different storage locations. |
| VER-90101 | SDK-Python | Due to the user's specific environment settings, the pip package had problems installing matplotlib-3.5.3 on the user's environment. There were no issues when installing newer versions of matplotlib. To avoid these install issues, install verticapy-1.0.0, which is compatible with the newer matplotlib versions. |
| VER-90115 | Scrutinize | Scrutinize no longer hangs when running "Command" tasks. |
| VER-90145 | UI - Management Console |
A custom alert was disabled if its query ran for more than 10 seconds. Now, the default timeout is 30 seconds. You can adjust this setting with the threshold_query.disable_time_out property in the /opt/vconsole/config/console.properties file. |
| VER-90855 | Optimizer | Create Table As Select statements with repeated occurrences of now() and similar functions were inserting incorrect results into the target table. The issue has been resolved. |
| VER-91148 | Data load / COPY | The upgrade of the C++ AWS SDK in 12.0.2 caused Vertica to make repeated calls to the metadata server for IAM authentication, affecting performance when accessing S3. Vertica now resets the timestamp to prevent excessive pulling. |