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.

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.

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 due to a limitation in Simba.

The LDAP authentication parameter starttls 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.

The following pypi packages were upgraded to fix CVE-2021-28363:

• urllib3 (1.26.5)
• bottle (0.12.20)

Calling "command_host -c start" or "restart_node" to start an EncryptSpreadComm-enabled database now gives a more useful error message, instructing users to call start_db instead.

In general, to start or stop an EncryptSpreadComm-enabled database, users should call start_db or stop_db.

Previously, changing the session timezone on the server did not affect the results returned when querying a timestamp. You could access the timestamp by calling getAdjustedTimestamp() on the result set object, but this was not functioning properly in binary transfer mode.

This issue has been resolved. In text and binary transfer modes, calling getAdjustedTimestamp() on a result set object returned by the server that contains a timestamp now properly returns the timestamp based on the timezone session parameter.

Users can now control configuration parameter MaxDVROSPerContainer knob and set it to any value >1. The new formula is:

max(2, (MaxDVROSPerContainer+1)/2)

A two-level strata helps avoid excessive DVMergeouts: DVs with fewer deleted rows than (TBL.nrows/MaxDVROSPerStratum), where maxDVROSPerStratun is max(2, (MaxDVROSPerContainer+1)/2), are placed at stratum 0; if the number of these DVs exceeds MaxDVROSPerStratum, they are merged together. As before, larger DVs at stratum 1 are not merged.

Users can now control configuration parameter MaxDVROSPerContainer knob and set it to any value >1. The new formula is:

max(2, (MaxDVROSPerContainer+1)/2)

A two-level strata helps avoid excessive DVMergeouts: DVs with fewer deleted rows than (TBL.nrows/MaxDVROSPerStratum), where maxDVROSPerStratum is max(2, (MaxDVROSPerContainer+1)/2), are placed at stratum 0; if the number of these DVs exceeds MaxDVROSPerStratum, they are merged together. As before, larger DVs at stratum 1 are not merged.

In Vertica 11.0, TLS configurations were greatly simplified for both LDAP Link and LDAP Authentication. As part of that simplification, the LDAP StartTLS parameter is now set automatically based on the TLSMODE and no longer needs to be set separately via a configuration parameter.

Previously, StartTLS was incorrectly enabled when using the ldaps:// protocol regardless of the TLSMODE. This issue has been resolved.

Vertica was unable to optimize queries on v_internal tables, where equality predicates (with operator =) filtered on columns relname or nspname, in the following cases:

• The predicate specified expressions with embedded characters such as underscore (_) or percentage (%). For example:

  SELECT * FROM v_internal.vs_columns WHERE nspname = 'x_yz';
  

• The query contained multiple predicates separated by AND operators, and more than one predicate queried the same column, either nspname or relname. For example:

  SELECT * FROM v_internal.vs_columns WHERE nspname = 'xyz' AND nspname <> 'vs_internal';
  

In this case, Vertica was unable to optimize equality predicate nspname = 'xyz'.

In all these cases, the queries are now optimized as expected.

It was unsafe to reorder query predicates when the following conditions were true: The query contained a predicate on a projection's leading sort order columns that restricted the leading columns to constant values, where the leading columns also were not run-length encoded. A SIPS predicate from a merge join was applied to non-leading sort order columns of that projection.

This issue has been resolved: query predicates can no longer be reordered when it contains a predicate on a projection's leading sort order columns that restrict leading columns to constant values, where the leading columns are not run-length encoded.