JDBC complex types return NULL arrays as empty arrays. For example, when executing this SQL statement:

SELECT ARRAY[null,ARRAY[1,2,3],null,ARRAY[4,5],null] as array;

The array column the server returns will be:

[[],[1,2,3],[],[4,5],[]]

Because of the null values in the string literal, it should return this value:

[null,[1,2,3],null,[4,5],null]

This is a work around to a limitation in Simba.

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:

CREATE LIBRARY lib1 AS :lib1_path DEPENDS :numpy_path LANGUAGE 'Python'; DROP LIBRARY lib1; CREATE LIBRARY lib2 AS :lib2_path DEPENDS :sklearn_path LANGUAGE 'Python';

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.

An error occurred, where Vertica was scheduling to remove a storage container while restore/replicate was trying to install the same storage container. After the installation was done, the storage was removed by tombstone. FNF happens. Our old design to prevent this from happening was disabling tombstone before installing storages, and enabling tombstone again later, also clearing all reaper queues as well, but this can cause leaked files. Although the user can use clean_communal_storage() command to remove these files, it is better to improve the restore/replicate to avoid leaked files.

This issue has been fixed by scanning all storages in the snapshot to restore/replicate, and removing the storages from tombstone and reaper queue while keeping others untouched in tombstone/reaper queue, so that we can make sure there won't be FNF or leaked files.

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.

The following improvements have been made to LDAPLink:

• LDAP synchronizations have been optimized and now are much faster for nested groups.
• Query profiling now works with LDAP dryrun functions.

The following improvements have been made to LDAPLink:

• LDAP synchronizations have been optimized and now are much faster for nested groups.
• Query profiling now works with LDAP dryrun functions.

Previously, the connection property FastCursorClose was set to false by default, which prevented you from canceling sqlfetch(). You had to set it to true with conn.addToConnString("FastCursorClose=1"); to cancel requests.

FastCursorClose is now set to {{true}} by default.

Previously, when a cluster lost quorum and switched to read-only mode or stopped, some transaction commits in the queue might get processed. However, due to the loss of quorum, these commits might not have been persisted. These "transient transactions" were reported as successful, but they were lost when the cluster restarted.

Now, when Vertica detects a transient transaction, it issues a WARNING so you can diagnose the problem, and it creates an event in ACTIVE_EVENTS that describes what happened.

The "starttls" LDAP authentication parameter is no longer deprecated and should generally be used when the LDAPAuth TLS Configuration is not granular enough to handle your environment. For example, if you have several LDAPAuth servers and only some of them can handle TLS, use  ALTER AUTHENTICATION to set "starttls" to "soft" in your authentication record to make TLS a preference and not a requirement.

For details, see the Vertica documentation on [LDAP authentication parameters|https://www.vertica.com/docs/12.0.x/HTML/Content/Authoring/Security/ClientAuth/LDAPParameters.htm].

The "starttls" LDAP authentication parameter is no longer deprecated and should generally be used when the LDAPAuth TLS Configuration is not granular enough to handle your environment. For example, if you have several LDAPAuth servers and only some of them can handle TLS, you should set (using ALTER AUTHENTICATION) "starttls" to "soft" in your authentication record to make TLS a preference and not a requirement.

For details, see the Vertica documentation on LDAP authentication parameters.

On AWS, the control mode for Eon Mode databases must be set to pt2pt, not broadcast.

Previously, users had to manually set the control mode to pt2pt after migrating their Eon Mode database from on-prem to AWS. Vertica now detects whether the Eon Mode database is running on AWS, and if so, sets the control mode to pt2pt when running revive_db.

In Kubernetes environments, it was possible to report the memory usage in the memory_usage view as a negative value. This occurred because the overall memory size in the system was reduced, but the other memory usage components, like bytes free, were not reduced. Because memory usage was reported at the host level, we reported the usage as a negative percentage when free memory was greater than total memory.

This issue has been resolved. Now, Kubernetes environments gather all memory information from cgroup information (/sys/fs/cgroup/memory) rather than /proc/memory.