Resolved issues
Resolved issues release notes for 24.2.x.
24.2.0-7
Updated 11/07/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-97542 | 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. |
24.2.0-6
Updated 10/21/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-97025 | 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-97234 | Data load / COPY | Previously, when querying certain ORC/Parquet files in a certain way, a hang would occur. This issue has now been fixed. |
| VER-97339 | Optimizer | A join spill was happening when processing the optimized delete part of the plan, which disallows Filter/Filter join distribution (the join inner was too large to fit in memory, which resulted in an error with a hint to retry with Filter/Filter enabled, even though it is already enabled in the session). This issue has been resolved; to address this, if 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. |
24.2.0-5
Updated 10/21/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-96758 | UI - Management Console | The system now allows the addition of LDAP users with numeric usernames in the Management Console. |
| VER-96808 | UI - Management Console | Entering email addresses for Federated accounts is optional; some users encountered an issue, where they couldn't alter LDAP objects to add email attributes to those objects. This issue has been resolved. Now, this attribute is not mandatory. |
| VER-96867 | Security | Clients not sending packets during initialization of TLS connections will no longer cause CPU usage to spike. |
| VER-97116 | UI - Management Console | An issue occurred after users upgraded their cluster from v11 to v12, where the Management Console did not properly show profile data for running queries. This issue has been resolved. |
24.2.0-4
Updated 09/10/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-95661 | 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. |
| VER-95819 | 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 error has been resolved. |
| VER-95834 | UI - Management Console | There is an issue with URL parsing when redirecting to Keycloak from MC. The URL had the special character “OR” operator (||). This issue has been resolved. |
| VER-95962 | 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-96126 | Security | install_vertica will no longer prefer the system openssl library to 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. |
| VER-96228 | Backup/DR | Server-based replication with target namespace used to fail due to namespace name case sensitivity. This issue has been resolved. |
| VER-96250 | 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-96327 | 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-96386 | Backup/DR | VBR no longer requires compat-openssl11 to be installed on RHEL9 systems. |
24.2.0-3
Updated 07/26/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-94595 | 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-95103 | 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-95108 | Data load / COPY | Vertica is now handling the null file and a null found case outside the json object with fjsonparser. |
| VER-95200 | Optimizer | Under certain circumstances, partition statistics could be used in place of full table statistics, leading to suboptimal plans. This issue has been resolved. |
| VER-95248 | 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. The issue has been resolved. |
| VER-95549 | Execution Engine | Some users were experiencing nodes down while using more than two WITHIN groups in listagg. This issue has been resolved. |
24.2.0-2
Updated 07/10/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-93609 | 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-93923 | 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-93930 | 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-94142 | 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-94204 | 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-94352 | Depot | Depot fetch used to call the aws list request. This has been resolved and now doesn't. |
| VER-94400 | Installation: Server RPM/Deb | The vioperf on some RHEL9 machines would OOM (out-of-memory) if run. This issue has been resolved. |
| VER-94569 | 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. |
24.2.0-1
Updated 04/25/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-93249 | EON, S3 | Previously, FIPS-enabled databases crashed when Vertica accessed an S3 bucket. This issue has been resolved. |
| VER-93444 | 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-93526 | ComplexTypes, Kafka Integration | Loading JSON/Avro data with Kafka and Flex parsers into tables with many columns suffered from performance degradation. This issue has been resolved. |
24.2.0-0
Updated 04/25/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-84807 | Data load / COPY | In COPY, some missing error checks made it so certain invalid input could crash the database. This has been resolved. |
| VER-85160 | Client Drivers - VSQL | In some cases, setting VSQL_CLIENT_LABEL environment variable wouldn't properly be set the client label for the session. This has been fixed. You can verify the label for your current session by querying the system table V_MONITOR.SESSIONS. |
| VER-85379 | Spread |
Previously, when a Vertica node went down, the status of standby nodes in the [NODES|https://docs.vertica.com/latest/en/sql-reference/system-tables/v-catalog-schema/nodes/] system table could be shown as DOWN for a short period of time before switching back to STANDBY. This has been fixed. The status of standby notes will now either remain on STANDBY or can be changed temporarily to UNKNOWN if Spread is disrupted for a long period of time. |
| VER-85497 | 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-87864 | Procedural Languages | Fixed memory leaks that could occur with certain stored procedures. |
| VER-88209 | 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-88425 | 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-88529 | Installation Program |
When you installed Vertica on RHEL 9 with the install_vertica script, there was a message about a missing ] character. This issue has been resolved. |
| VER-88896 | 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-89117 | 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. |
| VER-89166 | Execution Engine |
A new view called statement_outcomes has been added. This view contains one record per session-statement describing the outcome: success/fail and, if the fail, then the reason behind it. For example, in case the INSERT query succeeds, but the subsequent related constraint check fails, the records for the statement will be success=false with the appropriate description in the "error" column. The query_requests view has not changed. For example, an INSERT statement with a constraint check will have two records: success for the query and success for the related constraint check. The new view is the consolidated statement view. For example, when it shows execution time for the statement, that includes the time of retries (if any happened). |
| VER-89170 | DDL - Table | Vertica has two ways of defining the maximum size of an array type: ARRAY[type, max_elements] and ARRAY[type](max_binary_size). Complex array bounds could previously only be defined with the first syntax, but now we support the second syntax as well. |
| VER-89469 | Backup/DR | Users can now specify a target namespace in the REPLICATE function to replicate data from a migrated Eon Mode database to other Eon Mode databases. |
| VER-89555 | 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 resolved. |
| VER-89804 | 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-89806 | 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-90079 | Installation Program |
The install_vertica script did not display information about the HTTPS service settings. This issue has been resolved. |
| VER-90081 | 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-90084 | Optimizer | Update statements with subqueries in SET clauses would sometimes return an error. This issue has been resolved. |
| VER-90186 | 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 alignment issue has been resolved. |
| VER-90402 | 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-90504 | Client Drivers - ADO | Previously, the ADO.NET driver could give the "Invalid type: Guid" error when filtering for or querying UUID columns. This issue has been resolved. |
| VER-90525 | 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-90590 | 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 fixed. |
| VER-90947 | 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-90974 | Build and Release, Client Drivers - ODBC, Client Drivers - VSQL | The Linux ODBC driver and vsql client binaries have been stripped, significantly reducing their sizes. To get non-stripped binaries, please contact support. |
| VER-91232 | Catalog Engine | Previously, syslog notifiers could cause the node to go down when attached to certain DC tables. This issue has been resolved. |
| VER-91245 | 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-91271 | Optimizer | Queries using the same views repeatedly would sometimes return errors if those views included WITH clauses. The issue has been resolved. |
| VER-91423 | Execution Engine | When converting strings to numeric using the binary scale notation, using some very large powers would cause internal calculations to overflow, bypass some syntax checks, and crash. This has been resolved – the syntax checks now account for those large powers. |
| VER-91426 | UI - Management Console | The Management Console failed to start on Red Hat 8 because the default timeout to start an application with systemctl is not long enough. To resolve this issue, set the TimeoutStartSec service property for the vertica-consoled service to 300 seconds. |
| VER-91430 | 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-91432 | Logging | The LogRotate metafunction and timer service now support dbLog files. |
| VER-91553 | 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-91563 | Kafka Integration | When you did not provide the host parameter when you defined a cluster with the vkconfig command, you received an unclear error. This issue has been resolved. |
| VER-91696 | 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-91797 | Client Drivers - Misc |
In SQLTools Vertica driver versions 0.0.2 and later, the sessions table populates the following columns:
|
| VER-92058 | Scrutinize |
The scrutinize utility produces a tar file of the data it collects. Previously, scrutinize could fail to create this tar file if it encountered a broken symbolic link. This issue has been resolved, and the size of the tar file is now logged to scrutinize_collection.log. |
| VER-92223 | Data load / COPY | Previously Vertica had poor performance when loading wide tables using RecordParser that performs case-insensitive comparisons. This is now resolved. |
| VER-92298 | 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. |
| VER-92538 | UI - Management Console | When you upgraded the Management Console from version 12.0.4 to 23.3.0, log in to the Management Console failed and an error message displayed. This issue has been resolved. |
| VER-92542 | UI - Management Console | When you upgrade Management Console from version 12.0.4 to version 23.3.0, all users are migrated to Keycloak. The ldap password is saved to mconsole.log. |