Updated 6/16/2022

Important: Before Upgrading

Vertica for SQL on Hadoop Storage Limit

Vertica for SQL on Hadoop is licensed per node, on an unlimited number of central processing units or CPUs and an unlimited number of users. Vertica for SQL on Hadoop is for deployment on Hadoop nodes. Includes 1 TB of Vertica ROS formatted data on HDFS.

Starting with Vertica 10.1, if you are using Vertica for SQL on Hadoop, you cannot load more than 1 TB of ROS data into your Vertica database. If you were unaware of this limitation and currently have more than 1 TB of ROS data in your database, before upgrading to Vertica 10.1 or higher please make the necessary adjustments to stay below the 1 TB limit, or contact our sales team to explore other licensing options.

Identify and Remove Unsupported Projections

With version 9.2, Vertica has removed support for pre-join and range segmentation projections. If a table's only superprojection is one of these projection types, the projection is regarded as unsafe.Before upgrading to 9.2 or higher, you are strongly urged to check your database for unsupported projections. If the upgrade encounters these projections, it is liable to fail. You must then revert to the previous installation.

Solution: Run the pre-upgrade script

Vertica has provided a pre-upgrade script that examines your current database and sends to standard output its analysis and recommendations. The script identifies and lists any unsupported projections. If the script finds projection buddies with different SELECT and ORDER BY clauses, it generates a deploy script. Run this script to remedy projections so they comply with system K-safety.

https://www.vertica.com/pre-upgrade-script/

For more information, see Fixing Unsafe Buddy Projections in the Vertica documentation.

Contents

About Vertica Release Notes

Vertica 11.1.1

Vertica 11.1.0

About Vertica Release Notes

The Release Notes contain the latest information on new features, changes, fixes, and known issues in Vertica 11.1.x.

They also contain information about issues resolved in:

Downloading Major and Minor Releases, and Service Packs

The Premium Edition of Vertica is available for download at https://support.microfocus.com/downloads/swgrp.html.

The Community Edition of Vertica is available for download at https://www.vertica.com/download/vertica/community-edition.

The documentation is available at https://www.vertica.com/docs/11.1.x/HTML/index.htm.

Downloading Hotfixes

Hotfixes are available to Premium Edition customers only. Contact Vertica support for information on downloading hotfixes.

New in Vertica 11.1.1

See the Vertica 11.1.x New Features Guide for a complete list of additions and changes introduced in this release.

Configuration

Session-Level Support for SaveDCEEProfileThresholdUS

Configuration parameter SaveDCEEProfileThresholdUS can now be set at the session level.

Containers and Kubernetes

Operator Helm Chart Privileges with Service Accounts

Users that do not have cluster administrator privileges can install and run the operator by passing a custom service account with operator privileges to the serviceAccountNameOverride Helm chart parameter. The serviceAccountNameOverride parameter prevents the Helm chart from creating a default service account for the operator installation.

The cluster administrator must create the custom service account and grant it operator privileges before the non-admin user installs the Helm chart.

Install the Helm Chart without the Admission Controller Webhook

Users with limited permissions might want to install only the operator to manage Vertica on Kubernetes. The webhook.enable Helm chart parameter controls whether the Helm chart installs the admission controller webhook along with the operator.

Managed Kubernetes Services Support

Vertica supports managed Kubernetes services on Azure Kubernetes Service (AKS).

Air-Gapped Operator with Helm Chart

As a security feature, you can deploy the operator in an air-gapped cluster, which is a cluster that is disconnected from other networks. Use the following parameters to configure the isolated operator:

Customize LoadBalancer Service Types

Assign a static IP address for subclusters that use the LoadBalancer service type with the subcluster[i].loadBalancerIP parameter. This is useful for bare metal Vertica on Kubernetes deployments.

Add custom annotations to implementation-specific services with the subclusters[i].serviceAnnotations parameter. Managed Kubernetes offerings use annotations on service objects to control logging and other actions.

Configure Online Upgrade Traffic Redirect Wait Time

During an upgrade, the operator runs a reconcile iteration and requeues any resource objects for additional work if their actual state does not match the desired state. Set the upgradeRequeueTime parameter to determine how long the operator waits to complete any requeued work.

Database Management

Syslog Notifiers

You can now create notifiers that send messages to syslog.

Events monitored by this notifier type are not logged to MONITORING_EVENTS nor vertica.log.

Data Export

JSON Export

You can now export data to JSON files, including heterogeneous complex types.

Export to Single File

The following file exporters can now export all data to a single file:

If you choose to use this option, a single node performs the export.

Data Types

ROW and ARRAY Literals Support Nested Complex Types

When directly constructing ROW or ARRAY types, for example to use in a WHERE clause, you can now include fields and elements of these types.

Adding and Removing Columns of Complex Types

You can now use ALTER TABLE to add and remove columns of complex types. Previously, you could create a table with complex-type columns but could not add them to existing tables.

Geospatial Analytics

ST_GeomFromGeoJSON ignore_errors Parameter

The ST_GeomFromGeoJSON function has a new ignore_errors parameter. When set to true, it returns a NULL if the input GeoJSON fails to parse.

Use this setting when you are loading data that might contain faulty GeoJSON values. You can fill any faulty value's GEOMETRY column with NULL, and continue loading records.

Apache Hadoop Integration

WebHDFS Access with mTLS

For loading and exporting data, Vertica can access HDFS clusters protected by mTLS through the swebhdfs scheme. You must create a certificate and key and set the WebhdfsClientCertConf configuration parameter. The parameter value is a JSON string listing name services or authorities and their corresponding keys, so you can configure access to more than one HDFS cluster.

You can use CREATE KEY and CREATE CERTIFICATE to create temporary, session-scoped values. These keys and certificates are stored in memory, not on disk. You can set the configuration parameter at the session or database level.

Loading Data

Avro Maps

You can now treat an Avro map as an ARRAY[ROW]. The ROW fields must be named key and value. These are the names that the Avro format uses for those fields in the data, and the Avro parser relies on field names to match data to table columns.

Machine Learning

Support for XGBoost PMML Models

You can now import and export XGBoost PMML models. In PMML, an XGBoost model is an ensemble of TreeModels called a multiple model.

New probability_normalization parameter for PREDICT_XGB_CLASSIFIER and PREDICT_XGB_CLASSIFIER_CLASSES

Previously, the PREDICT_XGB_CLASSIFIER and PREDICT_XGB_CLASSIFIER_CLASSES functions used only the logit method to normalize the prediction probability of different classes. While these functions still use the logit method by default, this new parameter switches the normalization method to softmax.

Management Console

Eon Mode Subcluster and Node Actions Support for Microsoft Azure

Management Console supports the following new features for Microsoft Azure:

Query Optimization

Materialized WITH Clause Now Supported Using EE5 Temp Relation

Previously, Vertica implemented WITH clauses by either rewriting WITH statements using subqueries, or materializing WITH queries into local temp tables. By default, Vertica now executes WITH clause queries in sections of a multi-part plan and saves their output in EE5 temp relations. This update improves overall performance of WITH clauses.

SDK Updates

Reporting Errors and Warnings (Python)

You can now use a UDx written in Python to report errors, warnings, and other messages to the client. A message can contain a details string and a hint, like the messages that Vertica itself reports. The interface is similar to the C++ reporting API.

 

Security and Authentication

OAuth

Okta Support

Vertica now supports Okta as an identity provider (IDP) for OAuth authentication.

Empty Username and Password Requirement Removed (JDBC)

In 11.1.0, JDBC client applications that used OAuth had to pass an empty string for the user and password parameters in the connection string to authenticate. This parameter is no longer required when authenticating with OAuth.

Discovery URL Parameter (Keycloak Only)

You can now specify a discovery URL for both an authentication record and JDBC/ODBC. The discovery URL is an endpoint that contains your identity provider's OpenID Provider Configuration Document. This parameter is only supported for Keycloak.

If specified as a connection property in JDBC or ODBC, the client drivers will automatically retrieve the token URL from the discovery URL.

Similarly, if specified as an authentication parameter in Vertica, Vertica will automatically retrieve the introspect_url from the discovery_url.

Scope Parameter

The optional scope parameter lets you define the extent of access granted by the access token.

GRANT/REVOKE ALTER on TLS CONFIGURATION

You can now delegate the management (adding or removing certificates, changing the TLSMODE, etc.) of TLS Configurations to users or roles by granting and revoking ALTER privileges.

SQL Functions and Statements

Multi-Row INSERT

You can use INSERT to insert multiple rows in the target table, by specifying multiple comma-delimited VALUES lists.

UPDATE Enhancements

The FROM clause of an UPDATE statement can now reference the target table, as follows:

FROM DEFAULT [join-type] JOIN dataset [ ON join-predicate ]

DEFAULT specifies the table to update. This keyword can be used only once in the FROM clause, and it cannot be used elsewhere in the UPDATE statement.

UPDATE statements also now support the following hints:

INFER_TABLE_DDL for Native and External Tables

The INFER_TABLE_DDL function inspects a data file in Parquet, ORC, or Avro format and returns a draft table definition. It supports native and external tables and replaces INFER_EXTERNAL_TABLE_DDL, which is now deprecated.

Aliases for Collection Functions

For compatibility with other database platforms, ARRAY_COUNT is now an alias of APPLY_COUNT and ARRAY_LENGTH is now an alias of APPLY_COUNT_ELEMENTS. ARRAY_COUNT and ARRAY_LENGTH are no longer deprecated.

Deprecated and Removed in 11.1.1

Vertica retires product functionality in two phases:

Deprecated

Functionality Notes
INFER_EXTERNAL_TABLE_DDL Replaced by INFER_TABLE_DDL

Removed

Functionality Notes
INFER_EXTERNAL_TABLE_DDL (path, table) syntax Replaced by USING PARAMETERS syntax and INFER_TABLE_DDL

Resolved in 11.1.1-3

Updated 06/16/2022

This release addresses the issues below.

Issue Key Component Description
VER-81388 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-82041 Execution Engine

Addition of configuration parameter EnablePredicateRemoval introduced performance regressions in certain queries. This regression has been corrected.

VER-82245 Execution Engine

There was a performance issue when you executed a query on the VARBINARY(16) data type. This issue has been resolved.

Resolved in 11.1.1-2

Updated 06/08/2022

This release addresses the issues below.

Issue Key Component Description
VER-81738 UI - Management Console Some cookie features were not set properly in HTTP headers. This issue has been resolved.
VER-81849 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-81913 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-82036 Execution Engine Changed misleading counter name from "number of bytes read from communal storage" to "number of bytes read from persistent storage".
VER-82038 UI - Management Console Version 5.1.6 of the Spring framework had a vulnerability that was resolved by updating to version 5.1.13.

Resolved in 11.1.1-1

Updated 05/19/2022

This release addresses the issues below.

Issue Key Component Description
VER-81388 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-81871 Security

Users synced from LDAP with an obsolete DN are orphaned. Previously, if you dropped these orphaned users and re-created them with LDAP Link, their roles were not preserved. This issue has been resolved: these types of users now retain their roles on re-creation with LDAP Link.

Resolved in 11.1.1

Updated 05/3/2022

This release addresses the issues below.

Issue Key Component Description
VER-53679 Optimizer Previously, live aggregate projections had difficulty rewriting AVG() if the argument was of type INT. This issue has been resolved.
VER-62937 Security Previously, when configuring Kerberos authentication, not configuring the KerberosRealm parameter would cause the database to go down. This has been fixed; if KerberosRealm is not specified, Vertica automatically retrieves the realm from the Kerberos server and creates the connection.
VER-65100 Backup/DR Running backup/restore on a cluster with non-permanent nodes led to a misleading failure. This issue has been resolved.
VER-72363 Backup/DR Before this fix, the restored global catalog objects are installed on all the executor nodes after GCLX. The long process of catalog installation could cause GCLX timeout. This fix installs the restored global catalog objects on all the executor nodes before GCLX.
VER-73776 Optimizer Adding a subcluster with a larger number of nodes to an EON cluster required an unexpectedly long amount of time. This issue has been resolved.
VER-76092 Data Networking In rare circumstances, depending on the customer's network settings, TCP connections could still be considered alive for nodes that recently went down. That could result in significant query stalls or indefinite session hangs without ability to cancel. The issue has been resolved with improved TCP connection handling.
VER-76948 UI - Management Console When an AWS cluster was scaled up, the MC did not load all data when a custom file system was detected, and the AWS key pair was not populated. These issues were resolved.
VER-79025 Data Removal - Delete, Purge, Partitioning, DDL - Table In the past, an ALTER table's partition using an existing partition expression's internal representation was treated as a different partition expression and reorganized partition storage containers. Now, it is treated as the same partition expression and does not require partition storage container reorganization.
VER-79357 Optimizer

The FROM clause of an UPDATE statement can now reference the target-table, as follows:

FROM DEFAULT [join-type] JOIN dataset [ ON join-predicate ]

DEFAULT specifies the table to update. This keyword can be used only once in the FROM clause, and it cannot be used elsewhere in the UPDATE statement.

VER-80051 Execution Engine Vertica may crash after queries or DML operations with a storage merge.
VER-80087 Optimizer Previously, DBD functions DESIGNER_ADD_DESIGN_QUERIES and DESIGNER_RUN_POPULATE_DESIGN_AND_DEPLOY only supported local file system locations as arguments. Now, they also support communal storage locations.
VER-80359 UI - Management Console When creating a cluster, Management Console included unsupported characters in the key pair name when it generated the cluster IAM role name, which blocked the creation process. This issue has been resolved: now, MC removes unsupported characters in the key pair name from the generated IAM role name.
VER-80361 Execution Engine

Unlike a regular outer join, an event series join pads output with some cached values that represent the columns of the mismatched side. Padding with nulls is required if no previous rows are available for interpolation. To process event series joins, cached rows are always initialized with nulls, then updated with values to represent the mismatched side if applicable.

When initializing cached rows with a schema that differed from what the join expected at that stage of the query plan, Vertica occasionally crashed. This issue has been resolved: now cached rows are initially set to null tuples, using the correct tuple schema.

VER-80384 UI - Management Console When creating a cluster, Management Console included unsupported characters in the key pair name when it generated the cluster IAM role name, which blocked the cluster creation process. This issue has been resolved: now, MC removes unsupported characters in the key pair name from the generated IAM role name.
VER-80416 Client Drivers - JDBC, Execution Engine Previously, when using the JDBC and ADO.net drivers with binary encoding, queries that contained NUMERIC literal expressions that used parameterized prepared statement queries--could have incorrect precision and scale. This issue has been resolved.
VER-80441 Backup/DR, Migration Tool After migrating a database from Enterprise to Eon mode, loading data into tables with unsegmented projections could fail with the error "Cannot plan query because no super projections are safe". This issue has been resolved.
VER-80496 UDX EDIT_DISTANCE allocates memory properly instead of using the limited stack memory which was causing crashes on very large strings.
VER-80530 Execution Engine Vertica evaluates IN expressions in several ways, depending on the right-hand side. If the right-hand side is a subquery, then Vertica evaluates the expression as a join; if it is a list of constant expressions, then Vertica evaluates the expression by building a hash table of constant values; and if the expression is anything else, then Vertica either errors out, or evaluates the expression by rewriting it into a logical disjunction. Detection for the third case was flawed, resulting in an expression being evaluated incorrectly, which sometimes resulted in a crash. This issue has been resolved.
VER-80537 UI - Management Console When you added an existing user to a Custom Threshold notification, the checkbox was not responsive. This issue was resolved
VER-80551 Control Networking Depending on the customer's network settings, TCP connections were occasionally considered alive for nodes that recently went down. This could cause significant query stalls or indefinite session hangs without the ability to cancel. The issue has been resolved with improved TCP connection handling.
VER-80552 AP-Geospatial STV_Create_Index can create incorrect indexes on large sets of polygons. Using these indexes might cause a query to fail or bring a node down. This issue has been resolved.
VER-80553 Execution Engine The REPLACE function returned incorrect results if it called the SPLIT_PART function as its second (target string) argument. This issue has been resolved.
VER-80568 Data Collector Setting an empty channel in SET_DATA_COLLECTOR_NOTIFY_POLICY is now disallowed.
VER-80575 Monitoring The ros_count column in system view projection_storage was removed in release 11.0.2. This column has been restored, as per requests from clients who used it for monitoring purposes.
VER-80637 Execution Engine As a performance optimization, Vertica analyzes whether expressions can be true or false over a range of values, to avoid evaluating that expression for each row in the range. The analysis function regexp_like() sometimes returned incorrect results when the regular expression contained characters that allowed a pattern to match zero times, such as "?" and "*". This issue has been resolved.
VER-80655 UI - Management Console Previously, MC saved a DBD-generated design only when database K-safety was set to 0. This, issue has been resolved: now MC saves the design irrespective of the K-safety setting.
VER-80697 UI - Management Console

Before the introduction of custom threshold, email will be sent on "critical" and "alert" priority. After the introduction of custom threshold we let the users to send emails on all priorities.

This change has been implemented on all Thresholds, but since "Node state change" is a different criteria, that changes are not in effect. Now we have changed "Node state change" threshold to send email on all alert priority.

VER-80728 Execution Engine Partition-ranged projections did not work well with tables with Numeric typed partition expressions--for example, using the date_part function in the partition expression. This issue has been resolved.
VER-80749 Admin Tools admintools -t re_ip options -T and -U did not update admintools.conf with the correct control messaging protocol. This issue has been resolved.
VER-80765 Admin Tools The admintools operation db_add_node failed if the first node in the cluster was down. This failure occurred because after adding the node, db_add_node would try to use the first node as the source node for syncing vertica.conf and spread.conf files. This issue has been resolved: now, Vertica uses any UP node as the source node for syncing.
VER-80823 Client Drivers - Misc, Security

Fixed an issue where some Kerberos configurations would become invalid after upgrading to Vertica 11.1.0-0.

A side effect of this fix is that OAuth authentication records created in 11.1.0-0 become invalid when upgrading to 11.1.0-1 or later. To fix this, drop and recreate these invalid OAuth authentication records.

VER-80859 UDX New system prerequisites have been added for compiling C++ user-defined extensions (UDXs). See "Setting up the C++ SDK" for more details. https://www.vertica.com/docs/11.1.x/HTML/Content/Authoring/ExtendingVertica/C++/C++SDK.htm
VER-80879 Data load / COPY Operations over directories containing large numbers of external data files on object stores consumed more CPU than expected. This issue affected planning for external table queries, COPY statements, and license auditing. An algorithmic change reduced the amount of CPU time used to perform these operations.
VER-80888 Admin Tools Attempts to run multiple databases on the same cluster failed, even though each database ran exclusively on a different set of nodes--for example, database A with nodes 1 through 5, database B on nodes 6 through 10. This issue has been resolved.
VER-80929 UI - Management Console When the Management Console is installed on a Linux server, some files are created in the /tmp folder. If these files are removed, the MC database is not restored and clients lose data during an upgrade. This issue has been resolved: the MC database is now restored after an upgrade.
VER-80982 Backup/DR Replication on an Eon mode database requires access to communal storage locations on the source and target clusters. Since the Vertica 11.0.x release, replication on a database that used MiniIO communal storage locations failed because local nodes did not map correctly to those locations. This issue has been resolved.
VER-80997 Backup/DR When running Eon mode replication tasks, vbr returned with an error when it tried to connect to Vertica through a non-primary subscriber node. This issue has been resolved.
VER-81035 Catalog Engine LDAPLink now holds the GCLX for less time when Vertica synchronizes users and groups from an LDAP server.
VER-81055 Optimizer Previously, if two SELECT clause subqueries matched exactly, the subquery reuse feature created two different VARs instead of a single VAR for both, resulting in the GROUP BY expression being unable to find the relevant expression for the second VAR generated. This issue has now been fixed by generating a single VAR when the subqueries match exactly.
VER-81063 Scrutinize Due to previous update on ATCommand method, the scrutinize functions are broken. This fix will resolve that issue.
VER-81238 Admin Tools Administration Tools no longer kills all cluster nodes after the default timeout if some nodes are still initializaing. Also, if users do not respond to the timeout prompt, Administration Tools continues to wait.
VER-81504 Security In order to mitigate CVE-2022-0778 we have upgraded the version of OpenSSL that we ship to 1.1.1n

Known issues in 11.1.1

No known issues in 11.1.1

New in Vertica 11.1.0

See the Vertica 11.1.x New Features Guide for a complete list of additions and changes introduced in this release.

Containers and Kubernetes

Red Hat OpenShift Support

Vertica on Kubernetes supports OpenShift, a hybrid cloud platform that adds security features and additional support to Kubernetes. The VerticaDB operator is available in the OpenShift OperatorHub as a community-based operator that supports OpenShift versions 4.8 and higher.

Vertica Server Online Upgrade

You can upgrade the Vertica server versions without taking your cluster offline. Set the new upgradePolicy custom resource parameter to upgrade one subcluster at a time without interrupting your database activity.

Managed Kubernetes Services Support

Vertica supports managed Kubernetes services on Google Kubernetes Engine (GKE).

Improved Logging with Helm Chart Installs

VerticaDB operators that were installed with Helm have additional logging features. You can specify whether the operator sends logs to standard output, or to a file in the operator pod filesystem. In addition, you can set logging levels with new Helm chart parameters.

Add Environment Variables to the Vertica Server Container

Use annotations in the custom resource to add environment variables in the Vertica server container.

Data Types

JSON and Avro Complex Types

The JSON and Avro parsers now support complex types with strong typing. This support is in addition to flexible complex types that use a VMap (LONG VARBINARY) column to hold complex types.

This change does not include KafkaAvroParser.

Casting Complex Types

Vertica now supports casting structs (the ROW type) and non-native arrays. When casting a ROW, you can change the names of the fields. When casting an array, you can change the bounds. When casting to a bounded native array, inputs that are too long are truncated. When casting to a non-native array (an array containing complex data types including other arrays), if the new bounds are too small for the data the cast fails.

Loading Data

Additional Parquet File Formats

The Parquet parser now supports the following:

Machine Learning

TensorFlow: Additional Support for INT and FLOAT types

Previous versions of Vertica supported the following data types:

Vertica 11.1 adds support for the following data types:

SDK Updates

Reporting Errors and Warnings (C++)

A new API allows a UDx written in C++ to report errors, warnings, and other messages to the client. A message can contain a details string and a hint, like the messages that Vertica itself reports.

Security and Authentication

PasswordLockTimeUnit

The security parameter PasswordLockTimeUnit specifies the number of days, hours, minutes, or seconds for which an account is locked after a specified number of FAILED_LOGIN_ATTEMPTS.

OAuth 2.0 Support

You can now create and manage OAuth 2.0 authentication records and allow JDBC and ODBC clients to verify with an identity provider and then authenticate to Vertica with an access token (rather than a username and password).

SQL Functions and Statements

INFER_EXTERNAL_TABLE_DDL Supports Avro Format

The INFER_EXTERNAL_TABLE_DDL function now supports input files in the Avro format, in addition to Parquet and ORC.

Stored Procedures

Execute with Definer's User-level Parameters

Stored procedures that use SECURITY DEFINER now execute with the definer's:

System Tables

New BUILD_INFO Column in NODES Table

The NODES system table contains a new column named BUILD_INFO. This column contains the version of the Vertica server binary that is running on the node.

New Status for NODE_STATE Column in NODES and NODE_STATES Tables

The NODE_STATE column in the NODES and NODE_STATES tables has a new status named UNKOWN. A node can be in this state when Vertica identifies it as part of the cluster, but cannot communicate with the node to determine its current state.

Deprecated and Removed in Vertica 11.1.0

Vertica retires product functionality in two phases:

Deprecated

No deprecated functionality in this release.

Removed

No removed functionality in this release:

Resolved in 11.1.0

Updated 02/24/2022

This release addresses the issues below.

Issue Key Component Description
VER-1596 Client Drivers - JDBC, Sessions Each Vertica node now uses TCP keepalive to detect if it is disconnected from and automatically free resources allocated for a client.
VER-73125 Recovery The Tuple Mover uses the configuration parameter MaxMrgOutROSSizeMB to determine the maximum size of ROS containers that are candidates for mergeout. After a rebalance operation, Tuple Mover now groups ROS containers in batches that are smaller than MaxMrgOutROSSizeMB. A ROS container that is larger than MaxMrgOutROSSizeMB is merged individually.
VER-77380 Optimizer, Performance tests Running analyze_statistics('') on a large catalog would sometimes run out of memory and (at best) fail or (at worst) trigger an "out of memory" in the kernel. This has been resolved.
VER-79545 DDL Previously, you could not resize a table column that was used to segment any of that table's projections. This restriction has been lifted. Now, ALTER TABLE...ALTER COLUMN can modify the column's data type so it is larger or smaller than before, as long as the new size does not affect existing data.
VER-79811 Backup/DR During backup, vbr sends queries to vsql and reads the results from each query. If the vsql output comprised multiple lines that ended with newline characters, vbr mistakenly interpreted the newline character to indicate the end of output from the current query and stopped reading. As a result, when vbr sent the next query to vsql, it read the unread output from the earlier query as belonging to the current query. This issue has been resolved: vbr now correctly detects the end of each query result and reads it accordingly.
VER-79902 Admin Tools create_db failed in FIPS mode. This issue has been resolved.
VER-79913 DDL Previously, IMPORT_STATISTICS was unable to import statistics from output generated by EXPORT_STATISTICS_PARTITION. This issue has been resolved.
VER-80002 Security ALTER TLS CONFIGURATION data_channel now validates that the specified certificate can be used for internode encryption.
VER-80038 DDL, Execution Engine The server crashed when system queries used large strings as predicate constants--for example, "table_name = ..." or "schema_name = ..." This issue has been resolved.
VER-80049 Kafka Integration, UI - Management Console Security vulnerabilities CVE-2021-44228 and CVE-2021-45046 were found in earlier versions of the log4j library used by the MC. The library has been updated to resolve this issue.
VER-80052 UI - Management Console This release updates the Management Console’s Log4j library. The updated library addresses the CVE-2021-44228 and CVE-2021-45046 security vulnerabilities found in earlier versions.
VER-80053 Kafka Integration This release updates the Kafka integration’s Log4j library. The updated library addresses the CVE-2021-44228 and CVE-2021-45046 security vulnerabilities found in earlier versions.
VER-80124 Execution Engine Certain queries with ill-formed predicates that contained a large number of fields caused Vertica to run out of memory while trying to return an error message. This issue has been resolved: now, Vertica can build and return error messages of the type operator-not-found, regardless of length.
VER-80227 ComplexTypes A bug in the code caused parsing of nested case statements to become inefficient. This resulted in much larger processing time for case statements with multiple levels of nesting. This issue has been resolved: processing of nested case statements is again linear in the number of nesting levels.
VER-80262 Backup/DR On LINUX_FILESYSTEM, when a snapshot was in progress, vertica called glob() on all storage containers and then called stat() to check container statistics. If an error occurred between these two operations, the backup operation failed. This issue has been resolved: on LINUX_FILESYSTEM, the snapshot now only calls stat() on storage containers.
VER-80316 ComplexTypes, Execution Engine Previously, expressions with "subquery.*" as arguments (not in the top level of a SELECT statement or subquery) could result in undefined behavior. This issue has been resolved. Now, whenever "subquery.*" appears as an expression argument, it expands into a complex ROW expression with one field for each of the subquery's columns.
VER-80388 Execution Engine, UDX As of 10.1, inline SQL functions could not be passed a volatile parameter if that parameter appeared multiple times in the function definition. As an inline function, RIGHT returned an error when it was called with a volatile user-defined aggregate function as its first parameter. This issue has been resolved: RIGHT is no longer an inline SQL function, and instead is now defined internally.
VER-80439 Kafka Integration KafkaExport returns when it detects that all messages were sent to Kafka, reducing execution time up to 10 seconds.
VER-80610 Client Drivers - JDBC, Execution Engine Previously, when using the JDBC and ADO.net drivers with binary encoding, queries that contained NUMERIC literal expressions that used parameterized prepared statement queries--for example, ?/10--could have incorrect precision and scale. This issue has been resolved.

Known issues in 11.1.0

No known issues in 11.1.0.


Legal Notices

Warranty

The only warranties for products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from Micro Focus required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice

© Copyright 2006 - 2022 Micro Focus, Inc.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.