Known issues
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.
23.3.0-0
Updated 07/05/2023
Issue Key | Component | Description |
---|---|---|
VER-85911 | Client Drivers - VSQL |
When you connect to your database, vsql can show the following message: {{Bad terminal type: "vt100". Will assume vt100.}} This message can be safely ignored. |
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-69803 | Hadoop | The infer_external_table_ddl meta-function will hang if you do not set authentication information in the current session when analyzing a file on GCP. |
VER-64916 | Kafka Integration | When Vertica exports data collector information to Kafka via notifier, the serialization logic does not properly handle Vertica internal data type translation. When importing or copying that data back into the Management Console, Vertica uses the raw data in Kafka and inserts garbled data into the extended monitoring database. |
VER-64352 | SDK |
Under special circumstances, a sequence of statements to create and drop Python libraries fails. For example, the following session statements attempt to create Python libraries lib1 and lib2:
Here, lib1 is a Python library that imports module numpy, while lib2 imports module sklearn, which relies on numpy. After lib1 is dropped, the CREATE LIBRARY statement for lib2 fails. |
VER-62983 | Hadoop | When hcatalogconnector schemas are created with custom_partitions enabled, poor performance has been observed when there are many (500+) partitions. By default, custom_partitions are disabled on hcatalogconnector schemas. |
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. |