This is the multi-page printable view of this section. Click here to print.
List of unresolved issues for this Vertica release version.
List of resolved bugs and fixes for all hotfixes in this Vertica release version.
Describes the new features introduced in this Vertica release, and provides references to detailed information in the documentation set.
Details all deprecated and removed functionality for this Vertica release version.
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.
Updated 07/26/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-78310 | Client Drivers - JDBC |
JDBC complex types return NULL arrays as empty arrays. For example, when executing this SQL statement: The array column the server returns will be: Because of the null values in the string literal, it should return this value: This is a work around to a limitation in Simba. |
| VER-78074 | Procedural Languages, UDX | Stored procedures that contain DML queries on tables with key constraints do not return a value. |
| VER-61420 | Data Removal - Delete, Purge, Partitioning | Partition operations such as move_partitions_to_table must split storage containers that have partitions that match and do not match the operation. Version 9.1 introduced an inefficiency where such a split can split a storage container into an extra storage container. In this case, the tuple mover eventually merged the extra container. |
| VER-61069 | Execution Engine | In very rare circumstances, if a Vertica process crashes during shutdown, the remaining processes might hang indefinitely. |
Updated 10/24/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-96870 | Security | Clients not sending packets during initialization of TLS connections will no longer cause CPU usage to spike. |
| VER-97020 | Admin Tools, Installation Program, Installation: Server RPM/Deb | The urllib3 version is now upgraded from 1.26.18 to 1.26.19. |
| VER-97024 | Optimizer | Between v12 and v24, a previous bugfix made it so null rows passed hash SIP filters. This led to a performance drop on queries that relied on SIPS to filter out nulls early. This has been resolved; now, SIP filters remove null rows again. |
| VER-97233 | Data load / COPY | Previously, when querying certain ORC/Parquet files in a certain way, a hang would occur. This issue has now been resolved. |
| VER-97338 | Optimizer | An issue occurred, where a join spill was happening when processing the optimized delete part of the plan, which disallows Filter/Filter join distribution. Since the join inner was too large to fit in memory, an error was returned with a hint to retry with Filter/Filter enabled, even though it was already enabled in the session. This issue has been resolved; to address this, when the EnableFilterFilter hint is encountered when it's already enabled, we check if it's an optimized delete plan and in that case retry with optimized delete disabled, allowing the optimizer to choose a Filter/Filter join distribution. |
| VER-97470 | Client Drivers - VSQL | There was an issue that was preventing disabling or enabling of subcluster interior load balancing from taking effect immediately because an internal cache was not being cleared. Using ALTER DATABASE to set the EnableInteriorLoadBalancing parameter would have no impact on the result of the DESCRIBE_LOAD_BALANCE_DECISION function, which in turn would not change load balancing behavior of clients. This problem has been resolved. |
| VER-97541 | Optimizer | The view referenced in the UPDATE's target list had its subquery pruned during query rewrite, which misaligned a predicate reference to it and caused it to return a null value. This issue has been resolved; now, subquery targets are not pruned from the top-level UPDATE query's target list, instead only pruning FROM subqueries. |
| VER-97558 | Procedural Languages | On Eon mode as of 24.3, stored procedures triggered by the scheduler could not see the current subscriptions, leading to failures for certain procedures. This has been resolved; now, scheduled stored procedures can see the subscriptions. |
Updated 09/13/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-95961 | Machine Learning | There is a corner case where an orphan blob may remain in a session when the training of an ML model is cancelled. This orphan blob could cause a crash if there was an attempt to train a model with the same name on the same session. This issue has been resolved. |
| VER-96227 | Backup/DR | Server-based replication with target namespace used to fail due to namespace name case sensitivity. This issue has been resolved. |
| VER-96249 | EON | Previously, in certain cases when a cancel occurred during Vertica uploads to the communal storage, the node would crash. This issue has now been resolved. |
| VER-96326 | Catalog Engine | Qualified schema names with namespaces have some restrictions, which led to instances of no results being returned. This issue has been resolved. Note: This issue only occurred with displaying the system table. |
| VER-96385 | Backup/DR | VBR no longer requires compat-openssl11 to be installed on RHEL9 systems. |
Updated 08/29/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-95818 | Execution Engine | An error in expression analysis for REGEXP_SUBSTR would sometimes lead to a crash when that function was in the join condition. This issue has been resolved. |
| VER-96125 | Security | install_vertica will no longer give preference to the system openssl library over the one shipped with Vertica on non-fips systems. If you would like to use the system openssl library, delete the openssl libraries located at /opt/vertica/lib. |
Updated 08/12/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-95247 | Optimizer | FKPK Joins over projections with derived expressions would put PK input on the Inner side, even when it was much bigger than FK input, which resulted in worse performance in some scenarios. This issue has been resolved. |
| VER-95548 | Execution Engine | An issue that caused a crash while using WITHIN GROUP () function with listagg has been fixed. |
| VER-95660 | Execution Engine | Due to a bug in the numeric division code, users would get a wrong result when evaluating the mod operator on some numeric values with large precision. This issue has been resolved. |
Updated 07/26/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-68811 | Optimizer | Previously, the row count was estimated for this query using the many-to-1 join logic because anti-join was not checked until later in the process. Now, estimating the cardinality for anti-join is correctly applied in this situation. |
| VER-87781 | Admin Tools | Admintools was returning a strange error message. This has been fixed by adding a check guard at the place that was returning the strange log information, and additionally adding more logs for cross checking. |
| VER-88219 | Optimizer | If ARGMAX_AGG and DISTINCT were both used in a query, an internal error was raised. This issue has been resolved. Now, this case raises an unsupported error message that includes a hint on how to rework the SQL query to avoid the error. |
| VER-91425 | FlexTable | The copy of multiple json files to Vertica table using fjsonparser() is successful now, which was causing the initiator node down issue before this fix. |
| VER-91661 | Execution Engine | If the bounds provided by table statistics are out of order (low bound > high bound) and one of the bounds is 0, division expression analysis can result in a crash. This is likely caused by bad data. This issue has been resolved. Now, integrity checks have been added so that if the bounds provided are out of order, a warning is reported and the out-of-order section of the table's range is considered unbounded. |
| VER-91739 | Installation: Server RPM/Deb | The vioperf on some RHEL9 machines would OOM (out-of-memory) if run. This issue has been resolved. |
| VER-91760 | Installation Program | Previously, the {{install_vertica}} script would return an error if it was unable to determine the device ID, which occurred if any file under /sys/block/{}sd_dir{}/dev/ was missing. This has been fixed; {{install_vertica}} now skips missing dev files, if any. |
| VER-92719 | EON, S3 | Previously, FIPS-enabled databases crashed when Vertica accessed an S3 bucket. This issue has been resolved. |
| VER-92780 | Execution Engine | Whether LIKE ANY / ALL read strings as UTF8 character sequences or binary byte arrays depended on whether the collation of the current locale was binary, leading to incorrect results when reading multi-character UTF8 strings in binary-collated locales. This has been resolved. Now, LIKE ANY / ALL always reads UTF8 character sequences, regardless of the current locale's collation. |
| VER-92996 | 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. |
| VER-93119 | Backup/DR | LocalStorageLocator did not implement the construct_new() method. When called, it fell back to the StorageLocation.construct_new() method, which raised an error. This issue has been resolved. LocalStorageLocator.construct_new() is now implemented. |
| VER-93162 | Kubernetes | A new container was published that had the security vulnerabilities resolved. The container can be found at this public repository: opentext/vertica-logger:1.0.1 |
| VER-93339 | Client Drivers - JDBC | Previously, the JDBC driver used the com.google.gson package as packaged by the original maven build. Now the classes have been shaded under com.vertica to avoid collisions with other versions of gson packages used. |
| VER-93452 | Kafka Integration | There's now a better log message for incompatible compression types. |
| VER-93531 | Client Drivers - ODBC |
The Windows DSN configuration utility no longer sets vertica as the default KerberosServiceName value when editing a DSN. Starting with version 11.1, providing a value causes the ODBC driver to assume the connection is using Kerberos authentication and communicates to the server that it prefers to use that authentication method, assuming that the user has a grant to a Kerberos authentication method. The KerberosServiceName value might be set in earlier versions of Windows ODBC DSNs. Clearing the value will resolve the issue. This issue only applies to users who have a Kerberos authentication method granted with a lower priority than other authentication methods and use the DSN configuration utility to set up a DSN on Windows. |
| VER-93656 | Catalog Engine | Removed noisy transaction distcall slow events, which could cause all transactions to be blocked when system bottleneck occurs. |
| VER-93773 | Data load / COPY | In rare cases, copying a JSON to a table using FJsonParser or KafkaJsonParser could cause the server to go down. This issue has been resolved. |
| VER-93774 | UI - Management Console | There is an issue with bad clusters in Management Console. This issue has been resolved. Now, the derby data is refreshed and the database is removed and again imported into Management Console. |
| VER-93809 | Catalog Engine | Improvements to mutex profiling have been added. |
| VER-93972 | Optimizer | When a table was queried with sampling, partition pruning was blocked because the system attempted to simultaneously reason about the original predicates and the random sampling predicate. This issue has been resolved. Now, expression analysis on the original predicates is done separately from the random sampling predicate. |
| VER-94024 | Catalog Engine | As dc_catalog_refcounts is useful only for debugging purposes, it is disabled by default. |
| VER-94030 | Basics | Setting SlowEventsProfilingFreq to 0 caused a cluster failure. This issue has been resolved. |
| VER-94039 | Data load / COPY | Vertica is now handling the null file and a null found case outside the json object with fjsonparser. |
| VER-94082 | Depot | Depot fetch used to call AWS list request, but now doesn't. |
| VER-94118 | Kafka Integration | The vkconfig --refresh-interval option now functions properly. Setting it to one hour will refresh the lane worker every hour. |
| VER-94158 | Depot | The subcluster-level depot pin policy became the cluster-level policy after upgrading to version 23.4 or later. This issue has been resolved. For users already using version 23.4 or later, subcluster-level depot policies must be recreated. |
| VER-95476 | Tuple Mover | After performing a reshard database, the Tuple Mover logged a large number of PURGE requests on a projection while resharded containers exist on that projection. This issue has been resolved. |