Updated 3/1/2023

About Vertica Release Notes

These release notes contain the latest information on new features, changes, fixes, and known issues in Vertica 12.0.x.

They also contain information about issues resolved in major and minor releases, service packs, and hotfixes.

Downloads

For Vertica major, minor, and service pack releases:

• Enterprise Edition: https://support.microfocus.com/downloads/swgrp.html
• Community Edition: https://www.vertica.com/download/vertica/community-edition

Hotfix releases: Contact Vertica support

Contents

Vertica 12.0.3

• New in Vertica 12.0.3
• Deprecated and Removed

• Resolved

  • 12.0.3-3

  • 12.0.3-1

  • 12.0.3-0

• Known Issues

Vertica 12.0.2

• New in Vertica 12.0.2
• Deprecated and Removed

• Resolved

  • 12.0.2-2

  • 12.0.2-1

  • 12.0.2-0

• Known Issues

Vertica 12.0.1

• New in Vertica 12.0.1
• Deprecated and Removed

• Resolved

  • 12.0.1-0

• Known Issues

Vertica 12.0.0

• New in Vertica 12.0.0
• Deprecated and Removed

• Resolved

  • 12.0.0-0

• Known Issues

Vertica 12.0.3

Deprecated and Removed in 12.0.3

Vertica retires product functionality in two phases:

1. Deprecated: Vertica announces deprecated features and functionality in a major or minor release. Deprecated features remain in the product and are functional. Published release documentation announces deprecation on this page. When users access this functionality, it may return informational messages about its pending removal.

   Deprecated in 12.0.2	Notes
   JDBC 4.0 and 4.1 support
   The following parameters for CREATE NOTIFIER and ALTER NOTIFIER: TLSMODE CA BUNDLE CERTIFICATE	Use the TLS CONFIGURATION parameter instead. For details, see Creating a Kafka Notifier.
   The TLSMODE PREFER parameter for CONNECT TO VERTICA.	Use the TLS CONFIGURATION parameter instead.

2. Removed: Vertica removes a feature in a major or minor release that follows the deprecation announcement. Users can no longer access the functionality, and this page is updated to verify removal. Documentation that describes this functionality is removed, but remains in previous documentation versions.

   No functionality was removed in this release.

Resolved in 12.0.3

12.0.3-3

Updated 03/01/2023

Issue Key	Component	Description
VER‑85643	Database Designer Core	DESIGNER_DESIGN_PROJECTION_ENCODINGS returned with an error if a period was embedded in the design name. This issue has been resolved.

12.0.3-1

Updated 02/08/2023

Issue Key	Component	Description
VER‑85014	Security	Enabling data-channel encryption with a self-signed certificate could cause the database to go down. This issue has been resolved.
VER-85070	UI - Management Console	Errors were appearing on Activity -> Table Utilization and Table Details pages of the MC. Those errors were related to the references of columns in system tables that have been deleted. The issue was resolved.
VER-85236	Security	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.

12.0.3-0

Updated 01/31/2023

Issue Key	Component	Description
VER-72373	UDX	Creation of SQL macros with MapJSONExtractor failed with a 0-length string error. This issue has been resolved.
VER-79167	Execution Engine	Table update operations that involved very long (> 1MB) row sizes attempted to preallocate more memory than was available to the resource pool, based on excessive block size calculations, and failed for lack of resourcer pool capacity. This issue was resolved by avoiding excessively large block sizes.
VER-80639	UI - Management Console	Removed references to the columns in system tables that have been deleted.
VER-81348	Procedural Languages	Previously, running ANALYZE_STATISTICS through a stored procedure without superuser privileges could cause the database to go down. This issue has been resolved.
VER-82297	Client Drivers - ODBC, Client Drivers - VSQL	vsql now dynamically links the kerberos library in macOS.
VER-83000	Optimizer	When UPDATE referenced a table column with an access policy, the access policy rule was applied twice instead of once. This issue has been resolved: now the access policy rule is applied only once.
VER-83292	Admin Tools	Recent Linux distributions such as RHEL 8 and Ubuntu 20 (and higher) introduced _bracketed paste mode_ which, if enabled, broke intall_vertica and re_ip. This issue has been resolved.
VER-83408	Optimizer	If a query with an ORDER BY clause also contained a WITH clause with its own ORDER BY clause, and configuration EnableWITHTempRelReuseLimit=1, Vertica occasionally crashed in the late stages of query planning. This issue has been resolved.
VER-83532	Optimizer	Queries with string expressions in SELECT statements that were part of other expressions and also contained constant expressions sometimes returned an error. The issue has been resolved.
VER-83609	Backup/DR	Backup and restore on FIPS-enabled systems using object storage systems such as S3 could fail due to unavailability of the MD5 checksum implementation. These operations do not use MD5 for security, and this issue was resolved by flagging the uses of MD5 as not-for-security, thus enabling its use even with FIPS mode enabled.
VER-83649	Kubernetes	The vdb-gen tool now picks the correct ksafety value from the database.
VER-83700	Storage and Access Layer	If you added a column to a table in an Eon database with active subscribers to the shard of a DOWN node, Vertica failed to create storage containers for that column. As a result, attempts to query that column failed. This issue has been resolved: given the same conditions, Vertica now returns an error on attempts to add a table column.
VER-83735	Optimizer	Queries with complicated WITH clauses sometimes hung in Materialized WITH mode when directed queries or saved query plans were present in a database. The issue has been resolved.
VER-83865	Cloud - Amazon, UI - Management Console	In MC for AWS, the i4i.8xlarge instance had both NVMe volumes assigned to temp. This issue has beenn resolved: now, temp and depot each have one NVMe volume.
VER-83943	Backup/DR, Optimizer	When shard segmentation bounds and non-resharded storage container segmentation bounds did not match, reshard_database() returned with an error, and a hint to recreate problematic tables with CREATE TABLE AS; however, the CREATE operation resulted in tables that were missing rows. This issue has been resolved by changing the hint guidance: export the table data, truncate the table, and then use COPY to reload the table with the exported data.
VER-83974	Data Export	Export to delimited did not allow the same character to be used for both 'escapeAs' and 'enclosedBy'. This restriction has been removed.
VER-83988	Admin Tools	admintools uses a pseudoterminal (ssh + expect) to transfer data between nodes. When sending data larger than 4k, successful transfer depends on disabling canonical mode in the pseudoterminal. In some cases, this setting was ignored. This issue has been resolved.
VER-84073	Backup/DR	The vbr listbackup task failed with an error when nodes in the configuration file's [mapping] section did not match the nodes in database. This issue has been resolved: listbackup now returns with a warning about nodes that are missing in the configuration file.
VER-84122	Optimizer	Optimizer did not recognize valid FK-PK joins in some multi-key joins over inputs with Unique/Primary Key constraints. This issue has been resolved.
VER-84141	Optimizer	In some cases, row count estimate for joins on complex predicates was inaccurate. Recent improvements have addressed this issue.
VER-84187	Admin Tools	The problem was environmental. Fixing the configuration of the CipherTrust encryption system resolved the problem.
VER-84250	SDK Loading	JSON data into a geospatial column (geometry or geography) using FJSONParser errored out with unknown data type error. This issue has been resolved.
VER-84475	Optimizer	Queries with several subqueries in SELECT that were are also in the GROUP BY clause sometimes returned with an error. This issue has been resolved.
VER-84674	Recovery	Recovery from scratch reset cpe to 0, but mergeout was disabled for the projection whose cpe was 0. This restriction has been removed to allow concurrent data loading.
VER-84783	ILM, Recovery	During recovery, bulk loads blocked application of missed partition events. This issue has been resolved: now, missed drop partition events are applied by acquiring a D lock instead of an O lock.

Known Issues in 12.0.3

None

Vertica 12.0.2

Deprecated and Removed in 12.0.2

Vertica retires product functionality in two phases:

1. Deprecated: Vertica announces deprecated features and functionality in a major or minor release. Deprecated features remain in the product and are functional. Published release documentation announces deprecation on this page. When users access this functionality, it may return informational messages about its pending removal.

   Deprecated in 12.0.2	Notes
   JDBC 4.0 and 4.1 support
   The following parameters for CREATE NOTIFIER and ALTER NOTIFIER: TLSMODE CA BUNDLE CERTIFICATE	Use the TLS CONFIGURATION parameter instead. For details, see Creating a Kafka Notifier.
   The TLSMODE PREFER parameter for CONNECT TO VERTICA.	Use the TLS CONFIGURATION parameter instead.

2. Removed: Vertica removes a feature in a major or minor release that follows the deprecation announcement. Users can no longer access the functionality, and this page is updated to verify removal. Documentation that describes this functionality is removed, but remains in previous documentation versions.

   No functionality was removed in this release.

Resolved in 12.0.2

12.0.2-2

Updated 12/12/2022

Issue Key	Component	Description
VER‑84523	Admin Tools	admintools uses a pseudoterminal (ssh + expect) to transfer data between nodes. When sending data larger than 4k, successful transfer depends on disabling canonical mode in the pseudoterminal. In some cases, this setting was ignored. This issue has been resolved.

12.0.2-1

Updated 11/28/2022

Issue Key	Component	Description
VER‑84166	Procedural Languages	Previously, running ANALYZE_STATISTICS through a stored procedure without superuser privileges could cause the database to go down. This issue has been resolved.
VER‑84169	Data Export	Export to delimited did not allow the same character to be used for both 'escapeAs' and 'enclosedBy'. This restriction has been removed.
VER‑84195	Storage and Access Layer	If you added a column to a table in an Eon database with active subscribers to the shard of a DOWN node, Vertica failed to create storage containers for that column. As a result, attempts to query that column failed. This issue has been resolved: given the same conditions, Vertica now returns an error on attempts to add a table column.
VER‑84239	Optimizer	Queries with string expressions in SELECT statements that were part of other expressions and also contained constant expressions sometimes returned an error. The issue has been resolved.
VER‑84243	Backup/DR	The vbr listbackup task failed with an error when nodes in the configuration file's [mapping] section did not match the nodes in database. This issue has been resolved: listbackup now returns with a warning about nodes that are missing in the configuration file.
VER‑84335	Backup/DR, Optimizer	When shard segmentation bounds and non-resharded storage container segmentation bounds did not match, reshard_database() returned with an error, and a hint to recreate problematic tables with CREATE TABLE AS; however, the CREATE operation resulted in tables that were missing rows. This issue has been resolved by changing the hint guidance: export the table data, truncate the table, and then use COPY to reload the table with the exported data.

12.0.2-0

Updated 11/17/2022

Issue Key	Component	Description
VER‑67030	Security	ALTER TABLE...OWNER TO now properly changes the owner of table comments and projections.
VER‑72375	ComplexTypes, Database Designer Core	When using DBD for encoding design on native tables with collection type columns (array/set), column statistics were ignored even when statistics for scalar type columns were available. This issue has been resolved: available statistics on scalar columns are now used in DBD encoding design.
VER‑73290	Documentation	The documentation was unclear regarding proper usage of the coercion operator ::!. This issue has been resolved: the documentation now states that this operator only applies to table data, otherwise it returns an error.
VER‑74015	Data load / COPY	For profiling COPY FROM STDIN, the data_bytes_loaded column of the dc_execution_summaries table reported an incorrect value of zero. This issue has been resolved: the column now reflects the total number of bytes transferred from the client.
VER‑74675	Documentation	Documentation's description of the algorithm that Database Designer uses to recommend replicated over segmented projections was incomplete. The issue has been resolved.
VER‑78428	UI - Management Console	If a database with extended monitoring enabled went down, its Extended Monitoring page displayed no data. This issue has been resolved.
VER‑79231	UI - Management Console	The Management Console Java version was upgraded to Java 11.
VER‑80367	Backup/DR	VBR uploads to S3 storage sometimes returned with error messages that the upload failed. This issue has been resolved: on receiving these messages, VBR now retries the upload operation.
VER‑81135	Documentation	Description of support for running multiple databases in the same cluster was updated.
VER‑81195	Documentation	The documentation's descriptiopn of upgrade paths was updated.
VER‑81454	AMI	The Vertica server AMI and SSH configurations were updated to use more secure ciphers.
VER‑81654	Installation Program	Previously, the Vertica installer logged into each host twice during install process. It now logs in just once, reducing the installation time.
VER‑82240	Optimizer	Queries such as INSERT SELECT with reused WITH queries that had multipart DML query plans returned with errors when executed on an EON cluster with subclusters . This issue has been resolved.
VER‑82430	Optimizer	Previously, duplicate join predicates in an event series join query caused Vertica to crash. This issue has been resolved: users now see results as expected when submitting queries with repeating predicates.
VER‑82691	UI - Management Console	Microsecond values for the TIMESTAMPTZ data type were truncated in the Management Console interface. This issue has been resolved. Now, database server timestamps with UTC offset values display properly.
VER‑82725	Client Drivers - JDBC, Sessions	JDBC now properly runs PreparedStatement.execute() for insert statements with complex types.
VER‑82785	UI - Management Console	Vertica packages for SUSE Linux Enterprise Server did not include the Apache Log4j JAR files required for extended monitoring. This issue has been resolved.
VER‑82928	EON, Tuple Mover	The MaxMrgOutROSSizeMB is now ignored for big resharded containers, allowing tuple mover to pick and remove the unnecessary data from big resharded containers one by one.
VER‑82959	Kafka Integration	Under certain conditions, Vertica crashed when exporting data to Kafka. This issue has been resolved.
VER‑82984	EON	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.
VER‑83003	Control Networking	Previously, addition of standby nodes changed the assignment of control nodes and number of fault groups. This issue has been resolved: standby nodes are no longer set as control nodes.
VER‑83068	Client Drivers - JDBC, Client Drivers - VSQL, Execution Engine	In the 12.0.0 release, the default values of Vertica KeepAlive parameters were non-NULL values, which overrode the equivalent kernel TCP keepalive parameters. This issue has been resolved: now, all Vertica KeepAlive parameters are set to 0 (NULL), so effective settings are obtained from TCP keepalive parameters.
VER‑83076	Security	In some cases, the LDAP Link service could fail to create users due circular assignment after the first synchronization. This has been fixed.
VER‑83150	UI - Management Console	If you used a small subnet on AWS, SSH connections timed out when you ran the upgrade_vertica script. This issue has been resolved.
VER‑83200	Data Removal - Delete, Purge, Partitioning	If insufficent resources were available to complete a background repartitioning task, the responsible thread failed to retry the operation. This issue has been resolved: a given background repartitioning request now has multiple chances to complete.
VER‑83214	SDK-Java	Java SDK function setRowFromMap used to raise a exception when writing to BINARY type columns with the standard type coercion. The issue was fixed. Now standard type coercion successfully writes byte data to binary columns.
VER‑83225	DDL	The REPLACE function occasionally produced a string that exceeded the maximum string length of 65000 octets, and returned with an error. This issue has been resolved: the function no longer creates a result string that exceeds 65000 octets.
VER‑83295	ComplexTypes, Optimizer	The parameter "TryPruneUnusedDataEdges" toggles an optimization which tries to identify data edges of a query plan which are not necessary to compute the final result. This optimization would raise an INTERNAL error in rare situations with queries that perform a network resegment. This issue has been fixed.
VER‑83323	Admin Tools	Works as expected: the installer option --accept-eula allows users to avoid admintools prompts.
VER‑83377	Optimizer	The path_id for StorageUnion and Sort operators was sometimes reported to be -1. This issue has been resolved: path_id is now reported correctly.
VER‑83436	Catalog Engine	System table vs_storage_reference_counts was not updating the counter values in column num_accesses. This issue has been resolved.
VER‑83517	Backup/DR	Previously, the vbr replicate task returned an error if the source and destination databases shared the same database name and IP addresses. This issue has been resolved: these restrictions no longer apply.
VER‑83798	Documentation	The section that describes the algorithm used by DBD to determine whether to recommend unsegmented projections contained a couple of typos. This issue has been resolved.
VER‑83809	Backup/DR	Backup and restore on FIPS-enabled systems using object storage systems such as S3 could fail due to unavailability of the MD5 checksum implementation. These operations do not use MD5 for security, and this issue was resolved by flagging the uses of MD5 as not-for-security, thus enabling its use even with FIPS mode enabled.
VER‑83900	Optimizer	If a query with an ORDER BY clause also contained a WITH clause with its own ORDER BY clause, and configuration EnableWITHTempRelReuseLimit=1, Vertica occasionally crashed in the late stages of query planning. This issue has been resolved.
VER‑83905	Cloud - Amazon, UI - Management Console	In MC for AWS, the i4i.8xlarge instance had both NVMe volumes assigned to temp. This issue has been resolved: now, temp and depot each have one NVMe volume.

Known Issues in 12.0.2

None

Vertica 12.0.1

Deprecated and Removed in 12.0.1

Vertica retires product functionality in two phases:

1. Deprecated: Vertica announces deprecated features and functionality in a major or minor release. Deprecated features remain in the product and are functional. Published release documentation announces deprecation on this page. When users access this functionality, it may return informational messages about its pending removal.

   No functionality was deprecated in this release.

2. Removed: Vertica removes a feature in a major or minor release that follows the deprecation announcement. Users can no longer access the functionality, and this page is updated to verify removal. Documentation that describes this functionality is removed, but remains in previous documentation versions.

   Removed in 12.0.1	Notes
   Internet Explorer 11	Internet Explorer 11 web browser is retired and out of support as of June 15, 2022.

Resolved in 12.0.1

12.0.1-0

Updated 08/31/2022

Issue Key	Component	Description
VER‑74916	Optimizer	REFRESH_COLUMNS on a table with a partition range projection returned an error if partitions in the target range were already merged with other partitions outside the specified range. REFRESH_COLUMNS now supports a Boolean ForceSplit parameter, by default set to true, which handles this case by forcing split partitioning.
VER‑78868	Cloud - Azure, UI - Management Console	If an Eon mode database used Microsoft Azure, Management Console was unable to use the user-assigned identities when system-assigned identity was enabled. This issue has been resolved: now MC can use a user-assigned identity when a system-assigned identity is enabled.
VER‑78873	Cloud - Azure, UI - Management Console	When provisioning new nodes on an Eon mode database running on Microsoft Azure and system-assigned identity was enabled, Management Console MC did not assign tags to support authentication of Vertica nodes. This issue has been resolved.
VER‑80763	Client Drivers - VSQL	The vsql client now returns an error code when it encounters an error while running a long query--for example, the query exceeds the resource pool's RUNTIMECAP setting.
VER‑81774	Execution Engine, Optimizer	If join output required sorting and was used by another merge join, but had multiple equivalent sort keys, the sort keys were not fully maintained. In this case, the query returned with incorrect results. This issue has been resolve by maintaining the necessary sort keys for merge join input.
VER‑81944	Cloud - Amazon, UI - Management Console	When a previously used IP address was repeated from the subnet, Management Console failed to add hosts to the cluster. This issue is now resolved.
VER‑82084	Catalog Engine	Previously, containers generated by reshard_database() could not be tracked. This issue has been resolved by adding a new old_storage_oid column to dc_roses_created. This column helps trace new containers to the original containers from which they were derived.
VER‑82093	Depot	If the depot had no space to download a new file, the data loading plan did not write the file to the depot. Instead, it viewed the file as already in the depot, and incorrectly returned an error that the file size did not match the catalog. This issue has been resolved: the data loading plan no longer regards the absent file as in the depot.
VER‑82097	EON, ResourceManager	Previously, altering the max size of resource pools for non-local subclusters sometimes returned an error. This issue has been resolved.
VER‑82151	ComplexTypes, FlexTable	When parsing arrays of primitive types using the JSON parser, COPY failed with a message about records being too large. This issue has been resolved.
VER‑82198	Execution Engine	The optimizer removes predicates from a query if expression analysis finds them to be true for entire storage containers. When the same predicate appeared multiple times in a given query, and one of those predicates passed expression analysis, sometimes the optimizer removed all instances of that predicate. This issue has been resolved: the optimizer no longer removes multiple instances of the same predicate when one of them passes expression analysis.
VER‑82290	Backup/DR	If you restored a backup to another database with a different communal storage location, startup on the target database failed if the database's oid was assigned to another object. This issue has been resolved.
VER‑82316	AP-Geospatial	In some cases, ST_GeomFromGeoJSON returned non-null results on null input. This issue has been resolved.
VER‑82327	ComplexTypes	The array_count function read all fields of a complex array from storage. Doing so resulted in high cost estimates and sub-optimal query plans. This issue has been resolved: array_count now reads only one field.
VER‑82341	Data Export, Data load / COPY, Hadoop	When reading partition values from file paths, values that contained a '/' character were being read incorrectly by Vertica. This issue has been resolved.
VER‑82395	Admin Tools	pexpect inefficiently closed potential file descriptors when the nofile limit was high, attempting to close all file descriptors whether they were open or closed. This issue has been addressed: when the number of file descriptors is ≤ 2000, pexpect uses closerange to close the file descriptors, as it preforms better than close in a loop. When the number of file descriptors > 2000, pexpect iterates over the file descriptors in /proc/self/fd, which contains open file descriptors only, and closes them.
VER‑82425	Cloud - Amazon, UI - Management Console	After using Management Console to revive a database in the cloud, the database sometimes failed to start because of a lost+found directory in the catalog path. This issue is now resolved.
VER‑82439	Execution Engine	Queries with multipart plans that produced large temporay relations sometimes failed to clean up temporary files. This issue has been resolved.
VER‑82444	Optimizer	Queries with a UNION on EON subclusters resegmented grouped UNION leg outputs, even if UNION legs were segmented on group keys. This issue has been resolved, thereby improving query performance.
VER‑82445	Execution Engine	In some queries with highly selective predicates, StorageMerge ran slower than expected, especially with higher CPU core counts. This issue has been resolved.
VER‑82486	Execution Engine	If the REPLACE function was called with an empty string as the replacement (third) argument, it always returned a single-character result. This issue has been resolved.
VER‑82489	DDL - Table	After renaming a table with ALTER TABLE, the DDL for its projections continued to reference the previous name as an alias of the new name. This issue has been resolved: when a table is renamed, the DDL of its projections is also updated.
VER‑82492	Database Designer Core	When Database Designer processed queries that referenced non-table objects such as projections with pre-aggregated data such as live aggregate projections, it sometimes failed or produced core dumps and database crashes. This issue has been resolved: now Database Designer skips queries of these types.
VER‑82502	Execution Engine	The makeutf8 function sometimes caused undefined behavior when given maximum-length inputs for the argument column type. This issue has been resolved.
VER‑82572	Documentation	The INSERT documentation erroneously cited an limitation of 2000 rows for multi-row INSERT statements. This limitation has been removed.
VER‑82576	Client Drivers - JDBC	When JDBC connected to the server with BinaryTransfer and the JVM timezone had a historical or future Daylight Saving Time (DST) schedule, querying DST start dates in the JVM timezone sometimes returned incorrect data. This issue has been resolved; however, performance of BinaryTransfer for DATE data is worse than that of TextTransfer.
VER‑82622	Execution Engine	The makeutf8 function sometimes caused undefined behavior when given maximum-length inputs for the argument column type. This issue has been resolved.
VER‑82676	Data load / COPY	Flex table parsers did not reserve enough buffer space to correctly process certain inputs to NUMERIC-type columns. This issue has been resolved.
VER‑82683	DDL	Vertica allows any partition expression that resolves to non-NULL values, even in cases where the expression columns originally contained NULL values. Conversely, Vertica no longer allows a partition expression that produces NULL values even if the expression columns contain no NULL values.
VER‑82729	Optimizer	Queries with complex WITH clauses that used materialized WITH were running out of memory at the parsing stage. This issue has been resolved.
VER‑82730	Execution Engine	When processing the LAST_VALUE() function, the sort column was initialized using the input column's data type. In cases where the data types of the input and sort columns differed, Vertica used the wrong null representation. This issue has been resolved: now, the sort column is correctly initialized as per the ORDER BY column data type.
VER‑83043	Client Drivers - JDBC, Sessions	JDBC now properly runs PreparedStatement.execute() for insert statements with complex types.

Known Issues in 12.0.1

None

Vertica 12.0.0

Deprecated and Removed

Vertica retires product functionality in two phases:

1. Deprecated: Vertica announces deprecated features and functionality in a major or minor release. Deprecated features remain in the product and are functional. Published release documentation announces deprecation on this page. When users access this functionality, it may return informational messages about its pending removal.

   Deprecated in 12.0.0	Notes
   hive_partition_cols parameter for PARQUET and ORC parsers	Use COPY...PARTITION COLUMNS instead. See Partitioned File Paths.
   The following ODBC/JDBC OAuth parameters: OAuthAccessToken/oauthaccesstoken OAuthRefreshToken/oauthrefreshtoken OAuthClientId/oauthclientid OAuthClientSecret/oauthclientsecret OAuthTokenUrl/oauthtokenurl OAuthDiscoveryUrl/oauthdiscoveryurl OAuthScope/oauthscope	Replaced by OAuthJsonConfig (ODBC) and oauthjsonconfig (JDBC).

2. Removed: Vertica removes a feature in a major or minor release that follows the deprecation announcement. Users can no longer access the functionality, and this page is updated to verify removal. Documentation that describes this functionality is removed, but remains in previous documentation versions.

   Removed in 12.0.0	Notes
   Mac 10.12	ODBC client driver supporT
   AWS Library (S3EXPORT)	Replaced by File Export.

Resolved in 12.0.0

12.0.0-0

Updated 06/17/2022

Issue Key	Component	Description
VER‑61257	Data load / COPY	The load option "ON EACH NODE" was developed. If data to be loaded resides under the same file path on the filesystem of multiple nodes, a query can be run with "ON EACH NODE" instead of "path ON node1, path ON node2, ...". This will load data from the same file path on every node where the data is available.
VER‑67109	Catalog Engine	In a database with large number of projections, querying system table vs_segment or views of vs_segment somettimes returned with an error that the MaxParsedQuerySizeMB limit had been exceeded. This issue has been resolved.
VER‑73674	Admin Tools	Adding two nodes to a one-node enterprise database required the database to be rebalanced and made K-safe. Attempts to rebalance and achieve K-safety on the admintool command line ended in an error, while attempts to update K-safety in the admintools GUI also failed. These issues have been resolved.
VER‑79756	Client Drivers - VSQL, Security	When TLSMode is set to require, vsql did not allow connections if the SSL certificates were expired. This issue has been resolved.
VER‑80448	UI - Management Console	Some cookie features were not set properly in HTTP headers. This issue has been resolved.
VER‑80619	Backup/DR	vbr calls to the AWS function DeleteObjects() did not gracefully handle SlowDown errors. This issue has been resolved by changing the boto3 retry logic, so SlowDown errors are less likely to occur.
VER‑80890	Catalog Engine	Vertica 10.1 added support for bounds to array types. The addition of these bounds made changes to "typemod," which has represented the details of a column (e.g. VARCHAR length, timestamp precision). The changes to "typemod" were not correctly accounted for in the "odbc_columns" and "jdbc_columns" metadata tables, which resulted in inconsistent TIMESTAMP column definitions. This issue has been fixed.
VER‑81033	Security	OpenSSL has been upgraded to 1.1.1n.
VER‑81074	Execution Engine	'= ANY' expressions on arrays expect an array literal expression argument. If the argument was a string_to_array function, Vertica tried to interpret it as an array literal and produced a wrong result. This issue has been resolved: before passing a string_to_array function as an argument to an ' = ANY' expression, Vertica now constant-folds the function into an array literal, so the '= ANY' expression' can read the argument as expected.
VER‑81121	Admin Tools	Attempts to replace a down node in the admintools GUI or on the command line by calling db_replace_node or restart_node with the --force option failed. This issue has been resolved.
VER‑81214	UI - Management Console	Previously, when the MC was configured to use LDAP authentication and the MC restarted or the machine rebooted, MC users would be unable to log in to the MC with LDAP authentication. The issue has been resolved.
VER‑81248	Admin Tools	In previous releases, the default setting to rotate admintools.log was set to monthly, which was too infrequent for many clients, given the rapid growth of log size. This issue has been resolved: the default rotation frequency for admintools.log is now set to daily. A minimum log size limit is also set, which prevents rotation of logs if their size is less than 512kb.
VER‑81318	UI - Management Console	In some circumstances, the MC browser session would timeout after a period of inactivity. This issue has been resolved.
VER‑81358	Execution Engine	Addition of configuration parameter EnablePredicateRemoval introduced performance regressions in certain queries. This regression has been corrected.
VER‑81418	EON, Subscriptions	When an Eon Mode database was in read-only mode, unsegmented projected queries failed. Now, unsegmented projected queries succeed if there are active replica shard subscriptions on at least one node.
VER‑81470	Tuple Mover	Mergeout plans converted StorageMerge to StorageUnion+Sort, which slowed down mergeout and adversely affeced performance. This issue has been resolved: StorageMerge is no longer converrted to StorageUnion+Sort.
VER‑81474	Execution Engine	Changed misleading counter name from "number of bytes read from communal storage" to "number of bytes read from persistent storage"
VER‑81526	Backup/DR	When vbr failed to launch vertica-download-file or vertica-download-file ended with error, vbr raised an error because it tried to load the error message as json. This issue has been resolved with more error handling.
VER‑81572	Kubernetes	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.
VER‑81639	Execution Engine	Running analyze_statistics sometimes caused significant, unexpected slowdowns on concurrent queries. This slowdown was most noticeable on subsecond queries with StorageMerge operators in the plan. This issue has been resolved.
VER‑81684	Client Drivers - ODBC	TIMESTAMPTZ and TIMETZ values map to SQL_TYPE_TIMESTAMP and SQL_TYPE_TIME types in the ODBC Specification and do not include the timezone. The ODBC driver handles them identically to the TIMESTAMP and TIMETZ types.
VER‑81692	Client Drivers - ODBC	Previously, the ODBC driver could crash when using OCaml due to a bug in the Simba SDK. Version 12.0 Vertica ODBC driver uses an updated version of the Simba SDK that fixes this issue.
VER‑81694	Catalog Engine	Queries on system view V_MONITOR.PARTITIONS occasionally returned with an error that the limit set by MaxParsedQuerySizeMB had been exceeded. This issue has been resolved.
VER‑81729	UI - Management Console	Management Console was unable to start a database if the URL for communal storage ended with a backslash ('/'). This issue has been resolved.
VER‑81751	Execution Engine	There was a performance issue when you executed a query on the VARBINARY(16) data type. This issue has been resolved.
VER‑81830	Security	Users synced from LDAP with an obsolete DN are orphaned. Previously, if you dropped these orphaned users and recreated them with LDAP Link, their roles would not be preserved. This issue has been fixed; these types of users now retain their roles on recreation with LDAP Link.
VER‑81845	Optimizer	Previously, if a partition range projection included a column defined by an expression derived from another table column, querying on the projection sometimes caused the server to crash. This issue has been resolved.
VER‑81920	Tuple Mover	For projections with partition grouping, Reshard Mergeout can now efficiently merge both resharded and regular containers placed in different layers of strata.
VER‑81986	Depot	In Eon Mode, if the service shard was a non-participating primary subscriber, it could not fetch data from communal storage and cache it in the depot. This issue has been resolved. Now, if a node is down and another node temporarily served the shard, it fetches the file from communal storage and caches it in the depot without evicting any data.
VER‑82102	Security	Previously, running LDAP_LINK_DRYRUN_SEARCH and LDAP_LINK_DRYRUN_SYNC without the optional parameter 'LDAPLinkJoinAttr' would cause the database to go down. This issue has been fixed.
VER‑82114	Catalog Engine, DDL, UDX	Previously, CREATE PROCEDURE would not properly check for duplicate formal parameters in cases where they only differed by letter case (that is, upper or lower). This issue has been fixed.

Known Issues in 12.0.0

Updated 06/17/2022

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.

Issue Key	Component	Description
VER‑61069	Execution Engine	In very rare circumstances, if a Vertica process crashes during shutdown, the remaining processes might hang indefinitely.
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‑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‑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: 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.
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‑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‑78074	Procedural Languages, UDX	Stored procedures that contain DML queries on tables with key constraints do not return a value.
VER‑78310	Client Drivers - JDBC	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.