11.1.x Resolved issues

11.1.1-25

Updated 12/01/2023

Issue Key	Component	Description
VER-88926	UI - Management Console	When you provisioned a new database on Amazon Web Services, the operation failed. This issue has been resolved. 在 Amazon Web Services 上配置新数据库时，操作失败。此问题已解决。
VER-89846	Data Collector	If a notifier was set for some DC tables and then subsequently dropped, it still remained present in those DC table policies. This could cause a very large number of messages in vertica.log and potential node crashes. The issue was resolved by making "DROP NOTIFIER" support the CASCADE logic. Without CASCADE, drop would fail for the notifiers still used by DC tables. 如果为某些 DC 表设置了通知程序，随后又将其删除，该通知程序仍然存在于这些 DC 表策略中。这可能导致 vertica.log 中出现大量消息并可能导致节点崩溃。通过使"DROP NOTIFIER"支持 CASCADE 逻辑，此问题已解决。如果没有 CASCADE，DC 表仍在使用的通知程序的删除将失败。
VER-89910	Security	Previously, when configuring a chain of certificates longer than a root CA certificate and a client certificate for internode TLS, the configuration would successfully be applied, but cause the cluster to shut down. This has been fixed. 以前，当配置比根 CA 证书和节点间 TLS 的客户端证书更长的证书链时，配置会成功应用，但会导致集群关闭。此问题已修复。
VER-90039	Kafka Integration	When a notifier was set for the NotifierErrors or NotifierStats Data collector (DC) tables, notifications sent with a Kafka notifier might cause a loop that produced an infinite stream of notifications. This might result in severely degradated node performance. This issue has been resolved. Now, notifications are disabled for these DC tables, and any existing notifiers have been removed from these tables. 当为 NotifierErrors 或 NotifierStats 数据收集器 (DC) 表设置通知程序时，使用 Kafka 通知程序发送的通知可能会导致循环，从而产生无限的通知流。这可能导致节点性能严重下降。此问题已解决。现在，这些 DC 表的通知已禁用，并且所有现有通知程序已从这些表中移除。
VER-90092	Security	In cases of intermittent network connectivity to an LDAP server, Vertica will now retry bind operations. 在与 LDAP 服务器的网络连接间歇性中断的情况下，Vertica 现在将重试绑定操作。

11.1.1-24

Updated 10/27/2023

Issue Key	Component	Description
VER-89827	Recovery	Certain rare sequences of memory allocations crashed Vertica. This occurred when you loaded a table with many fields while a node was down and the MaxTieredPoolScale configuration parameter was set to 22 or lower. This issue has been resolved. 某些罕见的内存分配序列导致 Vertica 崩溃。当您在节点关闭且 MaxTieredPoolScale 配置参数设置为 22 或更低时加载包含许多字段的表时，就会发生此情况。此问题已解决。

11.1.1-23

Updated 09/27/2023

Issue Key	Component	Description
VER-89337	Data Collector	In some environments the io_stats system view was empty. The monitoring functionality has been improved with better detection of I/O devices. 在某些环境中，io_stats 系统视图为空。监控功能已改进，可更好地检测 I/O 设备。

11.1.1-22

Updated 08/29/2023

Issue Key	Component	Description
VER-88498	Client Drivers - ODBC	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. 以前，连接属性 FastCursorClose 默认设置为 false，这阻止了您取消 sqlfetch()。您必须使用 conn.addToConnString("FastCursorClose=1") 将其设置为 true 才能取消请求。FastCursorClose 现在默认设置为 true。
VER-88549	Optimizer	Queries that contained a WITH query that was referred to more than once and also contained multiple distinct aggregates failed with a system error. This issue has been resolved. 包含多次引用的 WITH 查询且同时包含多个不同聚合的查询因系统错误而失败。此问题已解决。

11.1.1-21

Updated 08/29/2023

Issue Key	Component	Description
VER-87777	Admin Tools, Data Collector	If you revived a database and the EnableDataCollector parameter was set to 1, you could not start the database after it was revived. This issue was resolved. To start the database, disable the cluster lease check. 如果您恢复了数据库且 EnableDataCollector 参数设置为 1，则恢复后无法启动数据库。此问题已解决。要启动数据库，请禁用集群租约检查。
VER-87878	Catalog Engine	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. 以前，当集群失去仲裁并切换到只读模式或停止时，队列中的某些事务提交可能会被处理。但是，由于仲裁的丧失，这些提交可能未被持久化。这些"临时事务"被报告为成功，但在集群重新启动时丢失了。现在，当 Vertica 检测到临时事务时，它会发出警告以便您可以诊断问题，并在 ACTIVE_EVENTS 中创建一个描述发生情况的事件。
VER-87969	SDK	Previously, Vertica didn't allow Vertica UDX builds using gcc compiler versions 13 or higher. This restriction has been removed. 以前，Vertica 不允许使用 gcc 编译器版本 13 或更高版本进行 Vertica UDX 构建。此限制已被移除。
VER-87972	Kafka Integration	In some circumstances, there were long timeouts or the process might hang indefinitely when the KafkaAvroParser accessed the Avro Schema Registry. This issue has been resolved. 在某些情况下，当 KafkaAvroParser 访问 Avro Schema Registry 时，会出现长时间超时或进程可能无限期挂起。此问题已解决。
VER-88007	Execution Engine	Queries with large tables stopped the database because the indices that Vertica uses to navigate the tables consumed too much RAM. This issue has been resolved, and now the indices use less RAM. 查询大型表导致数据库停止，因为 Vertica 用于导航表的索引消耗了过多 RAM。此问题已解决，现在索引使用更少的 RAM。
VER-88128	EON	The sync_catalog function failed when MinIO communal storage did not meet read-after-write and list-after-write consistency guarantees. A check was added to bypass this restriction. However, if possible, users should make sure that their MinIO storage is configured for read-after-write and list-after-write consistency. 当 MinIO 公共存储不满足写后读和写后列一致性保证时，sync_catalog 函数失败。添加了一个检查以绕过此限制。但是，如果可能，用户应确保其 MinIO 存储已配置为写后读和写后列一致性。
VER-88207	Optimizer	In some query plans with segmentation across multiple nodes, we would get an internal optimizer error when trying to prune out unused data edges from the plan. This issue has been resolved. 在某些跨多个节点分段的查询计划中，当尝试从计划中修剪未使用的数据边时，会出现内部优化器错误。此问题已解决。
VER-88228	EON	In rare circumstances, the automatic sync of catalog files to the communal storage stopped working on some nodes. Users could still manually sync with sync_catalog(). The issue has been resolved. 在极少数情况下，目录文件到公共存储的自动同步在某些节点上停止工作。用户仍然可以使用 sync_catalog() 手动同步。此问题已解决。
VER-88283	Performance tests	In some cases, the NVL2 function caused Vertica to crash when it returned an array type. This issue has been resolved. 在某些情况下，NVL2 函数在返回数组类型时导致 Vertica 崩溃。此问题已解决。

11.1.1-20

Updated 07/12/2023

Issue Key	Component	Description
VER-87801	Optimizer	During the planning stage, updates on tables with thousands of columns using thousands of SET USING clauses took a long time. Planning performance for these updates was improved. 在规划阶段，使用数千个 SET USING 子句对包含数千列的表进行更新需要很长时间。这些更新的规划性能已改进。
VER-87964	Tuple Mover	The Tuple Mover logged a large number of PURGE requests on a projection while another MERGEOUT job was running on the same projection. This issue has been resolved. 当另一个 MERGEOUT 作业在同一投影上运行时，Tuple Mover 在投影上记录了大量的 PURGE 请求。此问题已解决。

11.1.1-19

Updated 06/22/2023

Issue Key	Component	Description
VER-86940	Data Export, S3	Export to Parquet sometimes logged errors in a DC table for successful exports. This has been corrected. 导出到 Parquet 有时会在 DC 表中记录成功导出的错误。此问题已纠正。
VER-87120	Kafka Integration, Security	Previously, using a Kafka Notifier with SASL_SSL or SASL_PLAINTEXT would incorrectly use SSL instead. This has been resolved. 以前，使用带有 SASL_SSL 或 SASL_PLAINTEXT 的 Kafka 通知程序会错误地使用 SSL。此问题已解决。
VER-87144	Catalog Engine	Truncating a local temporary table unnecessarily required a global catalog lock, as temporary tables are session scoped. This issue has been resolved. 截断本地临时表不必要地需要全局目录锁定，因为临时表是会话范围的。此问题已解决。
VER-87256	Optimizer	Merge queries with an INTO...USING clause that calls a subquery would sometimes return an error when merging into a table with Set Using/Default query columns. The issue has been resolved. 具有调用子查询的 INTO...USING 子句的合并查询，在合并到具有 Set Using/Default 查询列的表中时，有时会返回错误。此问题已解决。
VER-87259	Execution Engine	Because the explode function is a 1:N transform function, using ORDER BY in its OVER clause has an undefined effect. Previously, using an ORDER BY clause in the OVER clause of Explode could result in an INTERNAL error if the configuration parameter TryPruneUnusedDataEdges was set to 1. This issue has been resolved. 由于 explode 函数是一个 1:N 转换函数，在其 OVER 子句中使用 ORDER BY 会产生未定义的效果。以前，如果配置参数 TryPruneUnusedDataEdges 设置为 1，则在 Explode 的 OVER 子句中使用 ORDER BY 子句可能会导致内部错误。此问题已解决。
VER-87295	Optimizer	Queries eligible for TOPK projections that were also eligible for elimination of no-op joins would sometimes exit with internal error. The issue has been resolved. 符合 TOPK 投影条件且同时符合无操作连接消除条件的查询有时会因内部错误退出。此问题已解决。
VER-87434	ComplexTypes	The flex and kafka parsers would erroneously not respect the parameter "reject_on_materialized_type_error" in cases where an array was too large for the target column, and no element was rejected. Previously, such values would always be rejected. This has been corrected, and now if "reject_on_materialized_type_error" is false, those values will be set to NULL instead. 当数组对于目标列来说太大时，flex 和 kafka 解析器会错误地不遵循参数"reject_on_materialized_type_error"，且没有元素被拒绝。以前，此类值总是会被拒绝。此问题已纠正，现在如果"reject_on_materialized_type_error"为 false，这些值将被设置为 NULL。
VER-87443	Data load / COPY	In some circumstances, Parquet file row groups whose metadata field "TotalBytes" has the value 0 might not load. This issue has been resolved. 在某些情况下，元数据字段"TotalBytes"值为 0 的 Parquet 文件行组可能无法加载。此问题已解决。

11.1.1-18

Updated 05/25/2023

Issue Key	Component	Description
VER-87099	Execution Engine	When evaluating check constraints on tables with multiple projections with different sort orders, Vertica would sometimes read the data from the table incorrectly. This issue has been resolved. 在评估具有不同排序顺序的多个投影的表上的检查约束时，Vertica 有时会错误地从表中读取数据。此问题已解决。
VER-87103	ComplexTypes	Previously, the flex table and Kafka parsers could crash if they tried to load array data that is too large for the target table. This behavior was fixed but introduced a change where those array values would cause the whole row to be rejected instead of setting the array value to NULL. Now, the default behavior is to set the data cell to NULL if the array value is too large. This can be overridden with the "reject_on_materialized_type_error" parameter, which will have the rows be rejected instead. 以前，flex 表和 Kafka 解析器如果尝试加载对于目标表来说太大的数组数据可能会崩溃。此行为已修复，但引入了一个更改，即这些数组值会导致整行被拒绝，而不是将数组值设置为 NULL。现在，如果数组值太大，默认行为是将数据单元格设置为 NULL。可以通过"reject_on_materialized_type_error"参数覆盖此行为，这将导致行被拒绝。

11.1.1-17

Updated 04/25/2023

Issue Key	Component	Description
VER-86560	FlexTable	In some cases COMPUTE_FLEXTABLE_KEYS used to assign non-string data types to keys where string data type was more suitable. The algorithm was improved to prefer string types in those cases. 在某些情况下，COMPUTE_FLEXTABLE_KEYS 会将非字符串数据类型分配给更适合字符串数据类型的键。算法已改进，在这些情况下优先选择字符串类型。
VER-86651	ComplexTypes	The flex JSON and Avro parsers did not always correctly handle excessively large ARRAY[VARCHAR] inputs. In certain cases this would lead to undefined behavior resulting in a crash. This issue has been fixed. flex JSON 和 Avro 解析器并不总是能正确处理过大的 ARRAY[VARCHAR] 输入。在某些情况下，这会导致未定义的行为，从而导致崩溃。此问题已修复。

11.1.1-16

Updated 04/25/2023

Issue Key	Component	Description
VER-85163	Recovery	Scratch recovery reset cpe to 0, disabling mergeout; restriction removed to allow concurrent data loading. 临时恢复将 cpe 重置为 0，禁用 mergeout；已移除限制以允许并发数据加载。
VER-85649	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. 如果设计名称中嵌入了句点，DESIGNER_DESIGN_PROJECTION_ENCODINGS 返回错误。此问题已解决。
VER-86097	Execution Engine	Predicate reordering moved a comparison ahead of SIP filters incorrectly; reordering prevented when a stateful SIP filter requires specific order. 谓词重排序错误地将比较移到了 SIP 过滤器之前；当有状态的 SIP 过滤器需要特定顺序时阻止重排序。
VER-86130	Optimizer	Queries with deeply nested expressions caused nodes to crash due to stack overflow. This issue has been resolved: now, the query runs normally if stack overflow occurs during non-essential stages of query processing–for example, getting pretty print for the expressions; or the query fails with an error message that the query contained an expression too large to analyze. 具有深层嵌套表达式的查询因堆栈溢出导致节点崩溃。此问题已解决：现在，如果在查询处理的非必要阶段（例如，获取表达式的漂亮打印）发生堆栈溢出，查询将正常运行；或者查询失败，并显示一条错误消息，指出查询包含的表达式太大而无法分析。
VER-86281	Execution Engine	When pushing down predicates of a query that involved a WITH clause being turned into a shared temp relation, an IS NULL predicate on the preserved side of a left outer join was pushed below the join. As a result, rows that should have been filtered out were erroneously included in the result set. This issue has been resolved by updating the predicate pushdown logic. 当将涉及 WITH 子句的查询的谓词下推为共享临时关系时，左外连接保留侧的 IS NULL 谓词被推到连接下方。结果，本应被过滤掉的行被错误地包含在结果集中。此问题已通过更新谓词下推逻辑解决。
VER-86317	Optimizer	LIMIT k OVER (...) clauses incorrectly estimated output rows by k, where k was calculated for every partition in the OVER clause. This issue has been resolved: estimation of output rows is now derived from the OVER clause. LIMIT k OVER (...) 子句错误地用 k 估计了输出行，其中 k 是针对 OVER 子句中的每个分区计算的。此问题已解决：输出行的估计现在来自 OVER 子句。
VER-86319	Recovery	When you applied a swap partition event to one table, the other table involved in the swap partition event was removed from the dirty transactions list. This issue has been resolved, and now both tables involved in the swap partition event are in the dirty transactions list. 当您将交换分区事件应用于一个表时，交换分区事件中涉及的另一个表将从脏事务列表中移除。此问题已解决，现在交换分区事件中涉及的两个表都位于脏事务列表中。
VER-86341	AP-Geospatial	If you nested multiple geospatial functions, there was an issue finding usable memory that made the database crash. This issue has been resolved. 如果您嵌套了多个地理空间函数，则查找可用内存时会出现问题，导致数据库崩溃。此问题已解决。
VER-86342	Data load / COPY	A check to prevent TOCTOU (time of check to time of use) privilege escalations issued false positives in cases where a file is appended to during a COPY. This issue has been resolved: the check has been updated so it no longer issues a false positive in such situations. 为防止 TOCTOU（检查时间到使用时间）权限提升的检查，在 COPY 期间追加文件的情况下会发出误报。此问题已解决：检查已更新，因此在这种情况下不再发出误报。
VER-86347	Admin Tools, Security	Paramiko has been upgraded to 2.10.1 to address CVE-2022-24302. Paramiko 已升级至 2.10.1 以解决 CVE-2022-24302。

11.1.1-15

Updated 03/10/2023

Issue Key	Component	Description
VER-85071	UI - Management Console	Two MC Activity pages, Table Utilization and Table Details, erroneously referenced system table columns that were removed in an earlier release. This issue has been resolved. 两个 MC 活动页面（表利用率和表详细信息）错误地引用了早期版本中已移除的系统表列。此问题已解决。
VER-85385	Data Export	Previously, all exports to parquet/orc/delimited/JSON failed if the exported query invoked a multi-part query plan. This issue has been resolved. 以前，如果导出的查询调用了多部分查询计划，则所有导出到 parquet/orc/delimited/JSON 的操作都会失败。此问题已解决。
VER-85438	Optimizer	Queries containing WITH statements with sorted output referenced in a different way throughout the query sometimes returned erroneous results. The issue has been resolved. 包含 WITH 语句的查询，其中排序的输出在查询中以不同方式引用，有时会返回错误结果。此问题已解决。
VER-85439	Admin Tools	Installation of an external procedure wrote the copied file in strings rather than bytes. Length calculation errors occurred when Japanese, Chinese, or other special characters were inserted, causing discrepancies between byte and string lengths. This issue has been resolved by writing the copied file in bytes. 安装外部程序时，复制的文件以字符串形式写入，而不是以字节形式写入。插入日文、中文或其他特殊字符时出现长度计算错误，导致字节和字符串长度之间的差异。此问题已通过以字节形式写入复制的文件解决。
VER-85493	Tuple Mover	The Mergeout strata algorithm had a hidden overflow issue due to incorrect type casting for wide projections with more than 4095 columns. This issue has been resolved. 对于超过 4095 列的宽投影，由于不正确的类型转换，Mergeout 层算法存在隐藏的溢出问题。此问题已解决。
VER-85571	Catalog Engine	Array type bounds (added in 10.1) caused typemod changes not reflected in odbc_columns/jdbc_columns, producing inconsistent TIMESTAMP definitions; fixed. 数组类型边界（在 10.1 中添加）导致 typemod 更改未反映在 odbc_columns/jdbc_columns 中，产生不一致的 TIMESTAMP 定义；已修复。
VER-85803	Security	Patched libtar to protect against CVE-2021-33643, CVE-2021-33644, CVE-2021-33645, and CVE-2021-33646. 修补了 libtar 以防止 CVE-2021-33643、CVE-2021-33644、CVE-2021-33645 和 CVE-2021-33646。
VER-85949	Execution Engine	NULLIF errored on volatile input (e.g. RANDOM()); now accepts any input. NULLIF 对易变输入（如 RANDOM()）出错；现在接受任何输入。
VER-85950	Security	An LDAP exception occurred when an LDAP user name was modified manually in Vertica and conflicted with a new LDAP user, causing the initiator node to go down. This issue has been resolved. 当在 Vertica 中手动修改 LDAP 用户名并与新 LDAP 用户冲突时，发生 LDAP 异常，导致启动器节点关闭。此问题已解决。

11.1.1-14

Updated 02/02/2023

Issue Key	Component	Description
VER-85015	Security	Enabling data-channel encryption with a self-signed certificate could cause the database to go down. This issue has been resolved. 使用自签名证书启用数据通道加密可能导致数据库瘫痪。此问题已解决。
VER-85237	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, use ALTER AUTHENTICATION to set "starttls" to "soft" in your authentication record to make TLS a preference and not a requirement. "starttls" LDAP 身份验证参数不再被弃用，通常应在 LDAPAuth TLS 配置不够精细以处理您的环境时使用。例如，如果您有多个 LDAPAuth 服务器但只有其中一些可以处理 TLS，请使用 ALTER AUTHENTICATION 将身份验证记录中的"starttls"设置为"soft"，以使 TLS 成为首选项而不是要求。

11.1.1-13

Updated 01/06/2023

Issue Key	Component	Description
VER-84838	Optimizer	Queries with subqueries in SELECT that also appeared in GROUP BY sometimes errored; fixed. 在 SELECT 中有子查询且该子查询也出现在 GROUP BY 中的查询有时出错；已修复。

11.1.1-12

Updated 12/06/2022

Issue Key	Component	Description
VER-84315	Optimizer	Queries with ORDER BY and a WITH clause having its own ORDER BY crashed during planning with EnableWITHTempRelReuseLimit=1; fixed. 带有 ORDER BY 以及具有自身 ORDER BY 的 WITH 子句的查询，在 EnableWITHTempRelReuseLimit=1 时于规划期间崩溃；已修复。
VER-84411	Backup/DR	vbr raised errors because it tried to load error messages as JSON when vertica-download-file failed; improved error handling added. 当 vertica-download-file 失败时，vbr 尝试以 JSON 形式加载错误消息而引发错误；增加了改进的错误处理。
VER-84524	Admin Tools	admintools uses ssh+expect for inter-node transfers; data >4k failed when canonical mode was ignored. Setting is now properly respected. admintools 使用 ssh+expect 进行节点间传输；当规范模式被忽略时，大于 4k 的数据失败。现在设置被正确遵循。

11.1.1-11

Updated 11/18/2022

Issue Key	Component	Description
VER-83921	Optimizer	UPDATE on a column with an access policy applied the rule twice instead of once; now applied only once. 对具有访问策略的列进行 UPDATE 时，规则被应用了两次而不是一次；现在只应用一次。
VER-84167	Procedural Languages	Running ANALYZE_STATISTICS via stored procedure without superuser could crash the database; fixed. 通过存储过程在没有超级用户权限的情况下运行 ANALYZE_STATISTICS 可能导致数据库崩溃；已修复。
VER-84170	Data Export	Export to delimited didn't allow same character for 'escapeAs' and 'enclosedBy'; restriction removed. 导出到分隔符格式不允许 'escapeAs' 和 'enclosedBy' 使用相同字符；已移除限制。
VER-84173	Control Networking	Adding standby nodes changed control node assignment and fault groups; standby nodes no longer set as control nodes. 添加备用节点更改了控制节点分配和故障组；备用节点不再被设置为控制节点。
VER-84240	Optimizer	Queries with string expressions in SELECT that were part of other expressions and contained constants sometimes errored; fixed. 在 SELECT 中作为其他表达式一部分并包含常量的字符串表达式的查询有时出错；已修复。
VER-84244	Backup/DR	vbr listbackup failed when [mapping] nodes didn't match database nodes; now returns a warning instead. 当 [mapping] 节点与数据库节点不匹配时，vbr listbackup 失败；现在返回警告而非错误。

11.1.1-10

Updated 11/07/2022

Issue Key	Component	Description
VER-84194	Storage and Access Layer	Adding a column in Eon DB with active subscribers to a DOWN node's shard failed to create storage containers. Now returns an error on column addition instead. 在 Eon 数据库中为 DOWN 节点的分片添加列时，若有活跃订阅者，则无法创建存储容器。现在在添加列时返回错误。

11.1.1-9

Updated 11/01/2022

Issue Key	Component	Description
VER-83547	Catalog Engine	vs_storage_reference_counts wasn't updating num_accesses; fixed. vs_storage_reference_counts 未更新 num_accesses；已修复。
VER-83716	Client Drivers - JDBC, Client Drivers - VSQL, Execution Engine	In 12.0.0, Vertica KeepAlive defaults were non-NULL, overriding kernel TCP keepalive. Now all are set to 0, deferring to OS settings. 在 12.0.0 中，Vertica KeepAlive 默认值为非 NULL，覆盖了内核 TCP keepalive。现在所有值都设置为 0，交由操作系统设置处理。
VER-83732	UI - Management Console	timestamptz microsecond values truncated in MC; timestamps with zone offsets now display correctly. timestamptz 微秒值在 MC 中被截断；带时区偏移的时间戳现在正确显示。
VER-83750	Backup/DR	VBR S3 uploads that errored now retry automatically. 出错的 VBR S3 上传现在会自动重试。
VER-83830	Backup/DR	vbr replicate errored when source and destination shared name and IPs; restrictions removed. 当源和目标共享名称和 IP 时，vbr replicate 出错；已移除限制。
VER-83858	Backup/DR	Backup/restore on FIPS systems with S3 failed due to MD5 unavailability; MD5 usage flagged as not-for-security, enabling FIPS mode operation. 在 FIPS 系统上使用 S3 进行备份/恢复因 MD5 不可用而失败；MD5 使用被标记为非安全用途，从而支持 FIPS 模式操作。
VER-83862	Admin Tools	Bracketed paste mode on RHEL 8/Ubuntu 20+ broke install_vertica and re_ip; fixed. RHEL 8/Ubuntu 20+ 上的括号粘贴模式破坏了 install_vertica 和 re_ip；已修复。
VER-83887	Optimizer	INSERT SELECT with reused WITH queries and multipart DML plans errored on EON with subclusters; fixed. 带有重用 WITH 查询和多部分 DML 计划的 INSERT SELECT 在具有子集群的 EON 上出错；已修复。
VER-83908	Optimizer	Complicated WITH clauses hung in Materialized mode when directed queries or saved plans were present; fixed. 当存在定向查询或已保存计划时，复杂的 WITH 子句在物化模式下挂起；已修复。

11.1.1-8

Updated 09/30/2022

Issue Key	Component	Description
VER-83194	UI - Management Console	Extended Monitoring page showed no data after DB went down; fixed. 数据库关闭后扩展监控页面未显示数据；已修复。
VER-83376	Machine Learning	Rounding errors in tree-based algorithm inclusive lower bound caused unexpected behavior; fixed. 基于树的算法包含下限中的舍入错误导致意外行为；已修复。
VER-83401	Execution Engine	LAST_VALUE() sort column used wrong null representation when input and sort column data types differed; now initialized correctly per ORDER BY type. 当输入和排序列数据类型不同时，LAST_VALUE() 排序列使用了错误的 null 表示；现在根据 ORDER BY 类型正确初始化。
VER-83433	DDL	REPLACE function produced strings exceeding 65000 octets; no longer creates results exceeding that limit. REPLACE 函数生成了超过 65000 八位字节的字符串；不再创建超过该限制的结果。
VER-83481	Database Designer Core	DB Designer processing queries referencing projections with pre-aggregated data caused crashes; now skips such queries. 数据库设计器处理引用预聚合数据的投影的查询导致崩溃；现在跳过此类查询。
VER-83484	Security	LDAP Link failed to create users due to circular assignment after first sync; fixed. LDAP Link 在首次同步后因循环分配而无法创建用户；已修复。
VER-83486	ComplexTypes, Optimizer	TryPruneUnusedDataEdges raised INTERNAL error in rare cases with network resegment; fixed. TryPruneUnusedDataEdges 在罕见的网络重新分段情况下引发内部错误；已修复。

11.1.1-7

Updated 09/14/2022

Issue Key	Component	Description
VER-83146	Client Drivers - JDBC, Sessions	JDBC now properly runs PreparedStatement.execute() for insert statements with complex types. JDBC 现在能正确运行带有复杂类型的 insert 语句的 PreparedStatement.execute()。
VER-83149	EON, ResourceManager	Altering max size of resource pools for non-local subclusters sometimes errored; fixed. 修改非本地子集群的资源池最大大小时有时出错；已修复。
VER-83306	Kafka Integration	Vertica crashed when exporting data to Kafka under certain conditions; fixed. Vertica 在特定条件下导出数据到 Kafka 时崩溃；已修复。
VER-83399	Execution Engine	StorageMerge ran slower than expected in queries with highly selective predicates, especially on high-CPU-core systems; fixed. StorageMerge 在具有高选择性谓词的查询中运行速度低于预期，尤其是在高 CPU 核心系统上；已修复。

11.1.1-6

Updated 08/30/2022

Issue Key	Component	Description
VER-82766	Optimizer	Queries with complex materialized WITH clauses ran out of memory at parse stage; fixed. 带有复杂物化 WITH 子句的查询在解析阶段耗尽内存；已修复。
VER-82814	Data Export, Data load / COPY, Hadoop	Partition values from file paths containing '/' were read incorrectly; fixed. 从包含 '/' 的文件路径中读取的分区值不正确；已修复。
VER-82849	DDL - Table	After ALTER TABLE...RENAME, projection DDL still referenced the old name as an alias; projection DDL is now updated on rename. 在 ALTER TABLE...RENAME 之后，投影 DDL 仍将旧名称作为别名引用；投影 DDL 现在在重命名时更新。
VER-82865	DDL	Some UNION ALL queries failed with "Temp relation descriptor not provided"; fixed. 某些 UNION ALL 查询因"Temp relation descriptor not provided"而失败；已修复。
VER-82880	DDL	Vertica now rejects partition expressions producing NULL values even if source columns have no NULLs; previously allowed some edge cases. Vertica 现在拒绝生成 NULL 值的分区表达式，即使源列没有 NULL 值；以前允许某些边缘情况。
VER-82905	Depot	Insufficient depot space caused incorrect "file size did not match catalog" errors; fixed. depot 空间不足导致错误的"file size did not match catalog"错误；已修复。
VER-82941	Client Drivers - JDBC	JDBC BinaryTransfer with JVM timezones having historical/future DST schedules returned incorrect DST start dates; fixed (performance trade-off noted). 具有历史/未来夏令时时间表的 JVM 时区的 JDBC BinaryTransfer 返回了错误的夏令时开始日期；已修复（存在性能权衡）。
VER-82968	Data load / COPY	Flex parsers didn't reserve enough buffer for NUMERIC-type inputs; fixed. Flex 解析器没有为 NUMERIC 类型输入保留足够的缓冲区；已修复。
VER-82981	Execution Engine	Multipart-plan queries producing large temp relations failed to clean up temp files; fixed. 生成大型临时关系的多部分计划查询未能清理临时文件；已修复。
VER-83052	Cloud - Amazon, UI - Management Console	Repeated IP from subnet caused MC to fail adding hosts; resolved. 来自子网的重复 IP 导致 MC 添加主机失败；已解决。
VER-83053	Cloud - Amazon, UI - Management Console	After reviving a cloud database in MC, a lost+found directory in catalog path prevented startup; fixed. 在 MC 中恢复云数据库后，目录路径中的 lost+found 目录阻止了启动；已修复。
VER-83070	Admin Tools	pexpect inefficiently closed file descriptors when nofile limit was high; optimized — uses closerange for ≤2000 FDs, iterates /proc/self/fd for >2000. 当 nofile 限制很高时，pexpect 低效地关闭文件描述符；已优化 — 对 ≤2000 个 FD 使用 closerange，对 >2000 个遍历 /proc/self/fd。
VER-83071	Optimizer	UNION on EON subclusters resegmented grouped outputs unnecessarily; fixed, improving query performance. EON 子集群上的 UNION 不必要地重新分段了分组输出；已修复，提升了查询性能。
VER-83088	Backup/DR	vbr calls to AWS DeleteObjects() didn't handle SlowDown errors; boto3 retry logic changed to reduce likelihood. vbr 对 AWS DeleteObjects() 的调用未处理 SlowDown 错误；boto3 重试逻辑已更改以降低可能性。

11.1.1-5

Updated 08/03/2022

Issue Key	Component	Description
VER-82377	Admin Tools	Adding two nodes to a one-node enterprise DB failed in rebalance/K-safety steps; resolved in both CLI and GUI. 向单节点企业数据库添加两个节点在重平衡/K-safe 步骤中失败；CLI 和 GUI 中均已解决。
VER-82380	ComplexTypes, FlexTable	JSON parser COPY failed with "records too large" when parsing arrays of primitive types; fixed. JSON 解析器 COPY 在解析原始类型数组时因"records too large"而失败；已修复。
VER-82381	AP-Geospatial	ST_GeomFromGeoJSON returned non-null on null input; fixed. ST_GeomFromGeoJSON 在 null 输入时返回了非 null；已修复。
VER-82629	Client Drivers - VSQL	vsql returned no error code on long-query errors (e.g. RUNTIMECAP exceeded); fixed. vsql 在长查询错误（如超过 RUNTIMECAP）时未返回错误码；已修复。
VER-82635	Optimizer	Partition range projections with expression-based columns crashed the server on query; fixed. 具有基于表达式的列的分区范围投影在查询时导致服务器崩溃；已修复。
VER-82757	ComplexTypes	array_count read all fields of a complex array, causing high cost estimates; now reads only one field. array_count 读取了复杂数组的所有字段，导致高成本估计；现在只读取一个字段。
VER-82758	Execution Engine	Optimizer removed all instances of a predicate when only one passed analysis; no longer removes multiple instances. 当只有一个谓词实例通过分析时，优化器移除了所有实例；不再移除多个实例。
VER-82759	Execution Engine, Optimizer	Merge join input with multiple equivalent sort keys didn't maintain keys properly, causing incorrect results; fixed. 具有多个等效排序键的合并连接输入未能正确维护键，导致错误结果；已修复。
VER-82774	Execution Engine	makeutf8 caused undefined behavior with maximum-length inputs; fixed. makeutf8 在最大长度输入时导致未定义行为；已修复。
VER-82806	Backup/DR	Restoring a backup to a different communal storage location failed if the DB's oid was assigned elsewhere; fixed. 如果数据库的 oid 被分配到了其他地方，将备份恢复到不同的公共存储位置会失败；已修复。

11.1.1-4

Updated 07/14/2022

Issue Key	Component	Description
VER-81807	Catalog Engine	Querying vs_segment or its views in a DB with many projections exceeded MaxParsedQuerySizeMB; fixed. 在具有许多投影的数据库中查询 vs_segment 或其视图超过了 MaxParsedQuerySizeMB；已修复。
VER-82162	Security	Running LDAP_LINK_DRYRUN_SEARCH/SYNC without LDAPLinkJoinAttr crashed the database; fixed. 在没有 LDAPLinkJoinAttr 的情况下运行 LDAP_LINK_DRYRUN_SEARCH/SYNC 导致数据库崩溃；已修复。
VER-82188	Catalog Engine, DDL, UDX	CREATE PROCEDURE didn't check for duplicate params differing only by case; fixed. CREATE PROCEDURE 未检查仅大小写不同的重复参数；已修复。
VER-82664	Execution Engine	REPLACE with empty string as third argument returned single-character result; fixed. REPLACE 以空字符串作为第三个参数时返回了单字符结果；已修复。

11.1.1-3

Updated 06/16/2022

Issue Key	Component	Description
VER-81388	Admin Tools	Replacing a down node via GUI or db_replace_node/restart_node --force failed; fixed. 通过 GUI 或 db_replace_node/restart_node --force 替换故障节点失败；已修复。
VER-82041	Execution Engine	EnablePredicateRemoval caused performance regressions in certain queries; corrected. EnablePredicateRemoval 导致某些查询的性能退化；已纠正。
VER-82245	Execution Engine	Performance issue when querying VARBINARY(16) data type; fixed. 查询 VARBINARY(16) 数据类型时的性能问题；已修复。

11.1.1-2

Updated 06/08/2022

Issue Key	Component	Description
VER-81738	UI - Management Console	Cookie features not set properly in HTTP headers; fixed. Cookie 功能未在 HTTP 标头中正确设置；已修复。
VER-81849	Tuple Mover	Mergeout plans converted StorageMerge to StorageUnion+Sort, slowing performance; conversion no longer occurs. Mergeout 计划将 StorageMerge 转换为 StorageUnion+Sort，降低了性能；不再进行此转换。
VER-81852	UI - Management Console	MC couldn't start a database when communal storage URL ended with '/'; fixed. 当公共存储 URL 以 '/' 结尾时，MC 无法启动数据库；已修复。
VER-81913	Execution Engine	analyze_statistics caused slowdowns on concurrent queries, especially subsecond queries with StorageMerge; fixed. analyze_statistics 导致并发查询变慢，尤其是带有 StorageMerge 的亚秒级查询；已修复。
VER-82036	Execution Engine	Counter renamed from "number of bytes read from communal storage" to "number of bytes read from persistent storage". 计数器从"number of bytes read from communal storage"重命名为"number of bytes read from persistent storage"。
VER-82038	UI - Management Console	Spring framework vulnerability (version 5.1.6) resolved by updating to 5.1.13. Spring 框架漏洞（版本 5.1.6）已通过更新到 5.1.13 解决。

11.1.1-1

Updated 05/19/2022

Issue Key	Component	Description
VER-81388	Admin Tools	Same issue as listed in 11.1.1-3: replacing a down node with --force failed; resolved. 与 11.1.1-3 中列出的问题相同：使用 --force 替换故障节点失败；已解决。
VER-81871	Security	LDAP-synced users with obsolete DNs became orphaned; dropping and re-creating them with LDAP Link now preserves roles. 具有过时 DN 的 LDAP 同步用户成为孤立用户；使用 LDAP Link 删除并重新创建它们现在会保留角色。

11.1.1-0

Updated 05/03/2022

Issue Key	Component	Description
VER-53679	Optimizer	Live aggregate projections had difficulty rewriting AVG() on INT arguments; fixed. 实时聚合投影在重写 INT 参数的 AVG() 时遇到困难；已修复。
VER-62937	Security	Omitting KerberosRealm crashed the DB; now Vertica retrieves the realm automatically from the Kerberos server. 省略 KerberosRealm 导致数据库崩溃；现在 Vertica 从 Kerberos 服务器自动获取 realm。
VER-65100	Backup/DR	Backup/restore on clusters with non-permanent nodes gave misleading failures; fixed. 在具有非永久节点的集群上进行备份/恢复给出了误导性错误；已修复。
VER-72363	Backup/DR	Restored global catalog objects were installed on all executor nodes after GCLX, causing timeouts; now installed before GCLX. 恢复的全局目录对象在 GCLX 之后安装到所有执行器节点上，导致超时；现在在 GCLX 之前安装。
VER-73776	Optimizer	Adding a larger-node subcluster to EON took unexpectedly long; fixed. 向 EON 添加更大节点的子集群花费了异常长的时间；已修复。
VER-76092	Data Networking	TCP connections considered alive for down nodes caused query stalls/hangs; improved TCP connection handling. 为故障节点认为 TCP 连接仍存活导致查询停顿/挂起；改进了 TCP 连接处理。
VER-76948	UI - Management Console	Scaled-up AWS clusters: MC didn't load all data with custom file systems, and key pair wasn't populated; issues resolved. 扩展的 AWS 集群：MC 未使用自定义文件系统加载所有数据，且密钥对未填充；问题已解决。
VER-79025	Data Removal - Delete, Purge, Partitioning, DDL - Table	ALTER TABLE partition using the same expression (internal representation) no longer reorganizes storage containers. 使用相同表达式（内部表示）的 ALTER TABLE partition 不再重新组织存储容器。
VER-79357	Optimizer	UPDATE FROM clause can now reference the target-table using "FROM DEFAULT [join-type] JOIN dataset". UPDATE FROM 子句现在可以使用"FROM DEFAULT [join-type] JOIN dataset"引用目标表。
VER-80051	Execution Engine	Vertica could crash after queries or DML with a storage merge; fixed. Vertica 在带有 storage merge 的查询或 DML 后可能崩溃；已修复。
VER-80087	Optimizer	DBD functions DESIGNER_ADD_DESIGN_QUERIES and DESIGNER_RUN_POPULATE_DESIGN_AND_DEPLOY now support communal storage locations. DBD 函数 DESIGNER_ADD_DESIGN_QUERIES 和 DESIGNER_RUN_POPULATE_DESIGN_AND_DEPLOY 现在支持公共存储位置。
VER-80359	UI - Management Console	MC removed unsupported characters from key pair names when generating IAM role names; resolved. MC 在生成 IAM 角色名称时移除了密钥对名称中的不支持的字符；已解决。
VER-80361	Execution Engine	Event series join crashes when cached rows were initialized with a schema differing from what the join expected; now uses correct tuple schema. 当缓存行使用与连接期望不同的模式初始化时，事件序列连接崩溃；现在使用正确的元组模式。
VER-80384	UI - Management Console	Same as VER-80359: unsupported characters in key pair names blocked cluster creation; fixed. 与 VER-80359 相同：密钥对名称中的不支持的字符阻止了集群创建；已修复。
VER-80416	Client Drivers - JDBC, Execution Engine	JDBC/ADO.net binary encoding with NUMERIC literal expressions in parameterized prepared statements had incorrect precision/scale; fixed. 在参数化预处理语句中使用 NUMERIC 字面量表达式的 JDBC/ADO.net 二进制编码具有错误的精度/小数位；已修复。
VER-80441	Backup/DR, Migration Tool	After migrating Enterprise to Eon mode, loading data into tables with unsegmented projections failed; fixed. 从 Enterprise 迁移到 Eon 模式后，向具有未分段投影的表加载数据失败；已修复。
VER-80496	UDX	EDIT_DISTANCE now allocates memory properly instead of using limited stack memory, preventing crashes on large strings. EDIT_DISTANCE 现在正确分配内存，而不是使用受限的堆栈内存，防止在大字符串上崩溃。
VER-80530	Execution Engine	Detection flaw for third-case IN expression evaluation caused crashes; fixed. 第三种情况 IN 表达式评估的检测缺陷导致崩溃；已修复。
VER-80537	UI - Management Console	Adding an existing user to a Custom Threshold notification had unresponsive checkbox; fixed. 将现有用户添加到自定义阈值通知时复选框无响应；已修复。
VER-80551	Control Networking	TCP connections considered alive for recently-downed nodes caused stalls/hangs; improved TCP handling. 为最近故障的节点认为 TCP 连接仍存活导致停顿/挂起；改进了 TCP 处理。
VER-80552	AP-Geospatial	STV_Create_Index created incorrect indexes on large polygon sets, causing query failures or node crashes; fixed. STV_Create_Index 在大型多边形集上创建了错误的索引，导致查询失败或节点崩溃；已修复。
VER-80553	Execution Engine	REPLACE returned incorrect results when SPLIT_PART was its second argument; fixed. 当 SPLIT_PART 是其第二个参数时，REPLACE 返回了错误结果；已修复。
VER-80568	Data Collector	Setting an empty channel in SET_DATA_COLLECTOR_NOTIFY_POLICY is now disallowed. 在 SET_DATA_COLLECTOR_NOTIFY_POLICY 中设置空通道现在已被禁止。
VER-80575	Monitoring	The ros_count column in projection_storage (removed in 11.0.2) has been restored. projection_storage 中的 ros_count 列（在 11.0.2 中移除）已恢复。
VER-80637	Execution Engine	regexp_like() returned incorrect results with zero-match patterns like "?" and ""; fixed. regexp_like() 使用"?"和""等零匹配模式时返回错误结果；已修复。
VER-80655	UI - Management Console	MC saved DBD-generated design only when K-safety=0; now saves regardless of K-safety setting. MC 仅在 K-safety=0 时才保存 DBD 生成的设计；现在无论 K-safety 设置如何都保存。
VER-80697	UI - Management Console	"Node state change" threshold now sends email on all alert priorities, aligning with other thresholds. "节点状态更改"阈值现在在所有警报优先级上发送电子邮件，与其他阈值保持一致。
VER-80728	Execution Engine	Partition-ranged projections didn't work well with Numeric partition expressions (e.g. date_part); fixed. 分区范围投影无法很好地与数字分区表达式（如 date_part）配合使用；已修复。
VER-80749	Admin Tools	admintools re_ip options -T and -U didn't update admintools.conf with correct control messaging protocol; fixed. admintools re_ip 选项 -T 和 -U 未使用正确的控制消息协议更新 admintools.conf；已修复。
VER-80765	Admin Tools	db_add_node failed when the first node was down; now uses any UP node as source for syncing config files. 当第一个节点关闭时，db_add_node 失败；现在使用任何 UP 节点作为同步配置文件的源。
VER-80823	Client Drivers - Misc, Security	Kerberos configurations invalid after upgrading to 11.1.0-0 fixed. Side effect: OAuth records created in 11.1.0-0 become invalid upgrading to 11.1.0-1+; must drop and recreate. 升级到 11.1.0-0 后 Kerberos 配置无效已修复。副作用：在 11.1.0-0 中创建的 OAuth 记录在升级到 11.1.0-1+ 时变为无效；必须删除并重新创建。
VER-80859	UDX	New system prerequisites added for compiling C++ UDXs; see "Setting up the C++ SDK" documentation. 添加了编译 C++ UDX 的新系统先决条件；请参阅"Setting up the C++ SDK"文档。
VER-80879	Data load / COPY	Operations over directories with many external files on object stores consumed excess CPU; algorithmic change reduced CPU usage. 在对象存储上对包含许多外部文件的目录进行操作消耗了过多 CPU；算法更改减少了 CPU 使用。
VER-80888	Admin Tools	Running multiple DBs on the same cluster with different node sets failed; fixed. 在同一集群上使用不同节点集运行多个数据库失败；已修复。
VER-80929	UI - Management Console	MC files in /tmp caused data loss on upgrade if removed; MC database now restored after upgrade. /tmp 中的 MC 文件在升级时如果被移除会导致数据丢失；MC 数据库现在在升级后恢复。
VER-80982	Backup/DR	Eon replication on MinIO communal storage failed because local nodes didn't map correctly (since 11.0.x); fixed. MinIO 公共存储上的 Eon 复制因本地节点映射不正确而失败（自 11.0.x 起）；已修复。
VER-80997	Backup/DR	vbr errored connecting to Vertica via non-primary subscriber during Eon replication; fixed. 在 Eon 复制期间，vbr 通过非主要订阅者连接到 Vertica 时出错；已修复。
VER-81035	Catalog Engine	LDAPLink now holds the GCLX for less time when synchronizing users/groups from LDAP. LDAPLink 现在在从 LDAP 同步用户/组时持有 GCLX 的时间更短。
VER-81055	Optimizer	Matching SELECT subqueries created two VARs instead of one, breaking GROUP BY expression matching; now generates a single VAR for identical subqueries. 匹配的 SELECT 子查询创建了两个 VAR 而不是一个，破坏了 GROUP BY 表达式匹配；现在为相同的子查询生成单个 VAR。
VER-81063	Scrutinize	scrutinize functions broken by a prior ATCommand update; fixed. scrutinize 函数被先前的 ATCommand 更新破坏；已修复。
VER-81238	Admin Tools	Admin Tools no longer kills all nodes after default timeout if some are still initializing; continues waiting if no user response. 如果某些节点仍在初始化，Admin Tools 不再在默认超时后杀死所有节点；如果没有用户响应则继续等待。
VER-81504	Security	OpenSSL upgraded to 1.1.1n to mitigate CVE-2022-0778. OpenSSL 已升级到 1.1.1n 以缓解 CVE-2022-0778。

11.1.0-0

Updated 02/24/2022

Issue Key	Component	Description
VER-1596	Client Drivers - JDBC, Sessions	Each Vertica node now uses TCP keepalive to detect disconnection and free client resources automatically. 每个 Vertica 节点现在使用 TCP keepalive 来检测断开连接并自动释放客户端资源。
VER-73125	Recovery	After rebalance, Tuple Mover groups ROS containers in batches smaller than MaxMrgOutROSSizeMB; oversized containers merged individually. 重平衡后，Tuple Mover 将小于 MaxMrgOutROSSizeMB 的 ROS 容器分批分组；过大的容器单独合并。
VER-77380	Optimizer, Performance tests	Running analyze_statistics('') on a large catalog ran out of memory and could trigger OOM in kernel; resolved. 在大型目录上运行 analyze_statistics('') 时内存耗尽，可能触发内核 OOM；已解决。
VER-79545	DDL	Restriction lifted: ALTER TABLE...ALTER COLUMN can resize a column used for segmentation as long as existing data isn't affected. 限制解除：只要不影响现有数据，ALTER TABLE...ALTER COLUMN 可以调整用于分段的列的大小。
VER-79811	Backup/DR	vbr misinterpreted newline characters in vsql multi-line output, causing misread results between queries; fixed. vbr 错误解释了 vsql 多行输出中的换行符，导致查询之间的结果误读；已修复。
VER-79902	Admin Tools	create_db failed in FIPS mode; fixed. create_db 在 FIPS 模式下失败；已修复。
VER-79913	DDL	IMPORT_STATISTICS couldn't import from EXPORT_STATISTICS_PARTITION output; resolved. IMPORT_STATISTICS 无法从 EXPORT_STATISTICS_PARTITION 输出导入；已解决。
VER-80002	Security	ALTER TLS CONFIGURATION data_channel now validates the certificate can be used for internode encryption. ALTER TLS CONFIGURATION data_channel 现在验证证书可用于节点间加密。
VER-80038	DDL, Execution Engine	Server crashed when system queries used large strings as predicate constants; fixed. 当系统查询使用大字符串作为谓词常量时，服务器崩溃；已修复。
VER-80049	Kafka Integration, UI - Management Console	log4j library updated to address CVE-2021-44228 and CVE-2021-45046. log4j 库已更新以解决 CVE-2021-44228 和 CVE-2021-45046。
VER-80052	UI - Management Console	MC Log4j library updated for CVE-2021-44228 and CVE-2021-45046. MC Log4j 库已更新以解决 CVE-2021-44228 和 CVE-2021-45046。
VER-80053	Kafka Integration	Kafka integration's Log4j library updated for CVE-2021-44228 and CVE-2021-45046. Kafka 集成的 Log4j 库已更新以解决 CVE-2021-44228 和 CVE-2021-45046。
VER-80124	Execution Engine	Ill-formed predicates with many fields caused OOM when building error messages; Vertica can now build operator-not-found messages regardless of length. 格式错误的谓词包含许多字段，在构建错误消息时导致 OOM；Vertica 现在无论长度如何都能构建 operator-not-found 消息。
VER-80227	ComplexTypes	Nested case statement parsing became inefficient (non-linear); processing restored to linear in nesting depth. 嵌套 case 语句解析变得低效（非线性）；处理已恢复到嵌套深度的线性。
VER-80262	Backup/DR	On LINUX_FILESYSTEM, errors between glob() and stat() during snapshots caused backup failure; snapshot now only calls stat() on storage containers. 在 LINUX_FILESYSTEM 上，快照期间 glob() 和 stat() 之间的错误导致备份失败；快照现在仅对存储容器调用 stat()。
VER-80316	ComplexTypes, Execution Engine	Expressions with "subquery." as arguments caused undefined behavior; now expands into a complex ROW expression with one field per subquery column. 以"subquery."为参数的表达式导致未定义行为；现在扩展为每子查询列一个字段的复杂 ROW 表达式。
VER-80388	Execution Engine, UDX	RIGHT function (previously inline) errored with volatile parameters; now defined internally instead of as an inline SQL function. RIGHT 函数（以前为内联）对易变参数出错；现在在内部定义，而不是作为内联 SQL 函数。
VER-80439	Kafka Integration	KafkaExport now returns immediately when all messages are sent, reducing execution time by up to 10 seconds. KafkaExport 现在在所有消息发送后立即返回，将执行时间减少多达 10 秒。
VER-80610	Client Drivers - JDBC, Execution Engine	JDBC/ADO.net binary encoding with NUMERIC literals in parameterized prepared statements had incorrect precision/scale; fixed. 在参数化预处理语句中使用 NUMERIC 字面量的 JDBC/ADO.net 二进制编码具有错误的精度/小数位；已修复。