Vertica 24.3.x BUG修复记录

simonchiang 2024-08-28

213

24.3.0-4

Updated 10/24/2024

Issue Key	Component	Description
VER-96870	Security	Clients not sending packets during initialization of TLS connections will no longer cause CPU usage to spike. 在 TLS 连接初始化期间不发送数据包的客户端将不再导致 CPU 使用率飙升。
VER-97020	Admin Tools, Installation Program, Installation: Server RPM/Deb	The urllib3 version is now upgraded from 1.26.18 to 1.26.19. urllib3版本现已从1.26.18升级到1.26.19。
VER-97024	Optimizer	Between v12 and v24, a previous bugfix made it so null rows passed hash SIP filters. This led to a performance drop on queries that relied on SIPS to filter out nulls early. This has been resolved; now, SIP filters remove null rows again. 在 v12 和 v24 之间，先前的错误修复导致空行通过了哈希 SIP 过滤器。这导致依赖 SIPS 尽早过滤掉空值的查询性能下降。这个问题已经解决；现在，SIP 过滤器再次删除了空行。
VER-97233	Data load / COPY	Previously, when querying certain ORC/Parquet files in a certain way, a hang would occur. This issue has now been resolved. 以前，当以某种方式查询某些 ORC/Parquet 文件时，会发生挂起。此问题现已解决。
VER-97338	Optimizer	An issue occurred, where a join spill was happening when processing the optimized delete part of the plan, which disallows Filter/Filter join distribution. Since the join inner was too large to fit in memory, an error was returned with a hint to retry with Filter/Filter enabled, even though it was already enabled in the session. This issue has been resolved; to address this, when the EnableFilterFilter hint is encountered when it’s already enabled, we check if it’s an optimized delete plan and in that case retry with optimized delete disabled, allowing the optimizer to choose a Filter/Filter join distribution. 出现一个问题，在处理计划的优化删除部分时发生连接溢出，这不允许 Filter/Filter 连接分布。由于连接内部太大而无法放入内存，因此返回了一个错误，并提示在启用 Filter/Filter 的情况下重试，即使会话中已启用它。此问题已解决；为了解决这个问题，当在已启用的情况下遇到 EnableFilterFilter 提示时，我们会检查它是否是优化删除计划，如果是，则在禁用优化删除的情况下重试，允许优化器选择 Filter/Filter 连接分布。
VER-97470	Client Drivers - VSQL	There was an issue that was preventing disabling or enabling of subcluster interior load balancing from taking effect immediately because an internal cache was not being cleared. Using ALTER DATABASE to set the EnableInteriorLoadBalancing parameter would have no impact on the result of the DESCRIBE_LOAD_BALANCE_DECISION function, which in turn would not change load balancing behavior of clients. This problem has been resolved. 由于未清除内部缓存，因此存在阻止禁用或启用子集群内部负载平衡立即生效的问题。使用 ALTER DATABASE 设置 EnableInteriorLoadBalancing 参数不会影响 DESCRIBE_LOAD_BALANCE_DECISION 函数的结果，进而不会改变客户端的负载平衡行为。此问题已解决。
VER-97541	Optimizer	The view referenced in the UPDATE’s target list had its subquery pruned during query rewrite, which misaligned a predicate reference to it and caused it to return a null value. This issue has been resolved; now, subquery targets are not pruned from the top-level UPDATE query’s target list, instead only pruning FROM subqueries. UPDATE 目标列表中引用的视图的子查询在查询重写期间被修剪，这会导致对它的谓词引用错位并导致其返回空值。此问题已解决；现在，不会从顶级 UPDATE 查询的目标列表中修剪子查询目标，而是仅修剪 FROM 子查询。
VER-97558	Procedural Languages	On Eon mode as of 24.3, stored procedures triggered by the scheduler could not see the current subscriptions, leading to failures for certain procedures. This has been resolved; now, scheduled stored procedures can see the subscriptions. 从 24.3 版开始，在 Eon 模式下，调度程序触发的存储过程无法查看当前订阅，从而导致某些过程失败。此问题已得到解决；现在，调度的存储过程可以查看订阅。

24.3.0-3

Updated 09/13/2024

Issue Key	Component	Description
VER-95961	Machine Learning	There is a corner case where an orphan blob may remain in a session when the training of an ML model is cancelled. This orphan blob could cause a crash if there was an attempt to train a model with the same name on the same session. This issue has been resolved. 有一种特殊情况，即当取消 ML 模型的训练时，孤立 blob 可能会留在会话中。如果尝试在同一会话中训练同名模型，此孤立 blob 可能会导致崩溃。此问题已解决。
VER-96227	Backup/DR	Server-based replication with target namespace used to fail due to namespace name case sensitivity. This issue has been resolved. 由于命名空间名称区分大小写，基于服务器的与目标命名空间的复制曾经失败。此问题已解决。
VER-96249	EON	Previously, in certain cases when a cancel occurred during Vertica uploads to the communal storage, the node would crash. This issue has now been resolved. 以前，在某些情况下，当 Vertica 上传到公共存储期间发生取消时，节点会崩溃。此问题现已解决。
VER-96326	Catalog Engine	Qualified schema names with namespaces have some restrictions, which led to instances of no results being returned. This issue has been resolved. Note: This issue only occurred with displaying the system table. 具有命名空间的合格schema名称有一些限制，这导致没有返回结果的情况。此问题已解决。注意：此问题仅在显示系统表时发生。
VER-96385	Backup/DR	VBR no longer requires compat-openssl11 to be installed on RHEL9 systems. VBR 不再需要在 RHEL9 系统上安装 compat-openssl11。

24.3.0-2

Updated 08/29/2024

Issue Key	Component	Description
VER-95818	Execution Engine	An error in expression analysis for REGEXP_SUBSTR would sometimes lead to a crash when that function was in the join condition. This issue has been resolved. REGEXP_SUBSTR 表达式分析中的错误有时会导致函数处于连接条件时崩溃。此问题已解决。
VER-96125	Security	install_vertica will no longer give preference to the system openssl library over the one shipped with Vertica on non-fips systems. If you would like to use the system openssl library, delete the openssl libraries located at /opt/vertica/lib. install_vertica 不会再在非 FIPS 系统上优先使用系统的 OpenSSL 库，而是使用 Vertica 自带的 OpenSSL 库。如果您想使用系统 openssl 库，请删除位于 /opt/vertica/lib 的 openssl 库。

24.3.0-1

Updated 08/12/2024

Issue Key	Component	Description
VER-95247	Optimizer	FKPK Joins over projections with derived expressions would put PK input on the Inner side, even when it was much bigger than FK input, which resulted in worse performance in some scenarios. This issue has been resolved. 使用派生表达式对投影进行 FKPK 连接会将 PK 输入放在内侧，即使它比 FK 输入大得多，这在某些情况下会导致性能下降。此问题已解决。
VER-95548	Execution Engine	An issue that caused a crash while using WITHIN GROUP () function with listagg has been fixed. 使用 WITHIN GROUP () 函数与 listagg 时导致崩溃的问题已修复。
VER-95660	Execution Engine	Due to a bug in the numeric division code, users would get a wrong result when evaluating the mod operator on some numeric values with large precision. This issue has been resolved. 由于数字除法代码中存在错误，用户在对某些精度较高的数值评估 mod 运算符时会得到错误的结果。此问题已解决。

24.3.0-0

Updated 07/26/2024

Issue Key	Component	Description
VER-68811	Optimizer	Previously, the row count was estimated for this query using the many-to-1 join logic because anti-join was not checked until later in the process. Now, estimating the cardinality for anti-join is correctly applied in this situation. 以前，使用多对一连接逻辑来估计此查询的行数，因为直到过程的后期才检查反连接。现在，在这种情况下可以正确应用估计反连接的基数。
VER-87781	Admin Tools	Admintools was returning a strange error message. This has been fixed by adding a check guard at the place that was returning the strange log information, and additionally adding more logs for cross checking. Admintools 返回了一条奇怪的错误消息。已通过在返回奇怪日志信息的地方添加检查保护并另外添加更多日志进行交叉检查来解决此问题。
VER-88219	Optimizer	If ARGMAX_AGG and DISTINCT were both used in a query, an internal error was raised. This issue has been resolved. Now, this case raises an unsupported error message that includes a hint on how to rework the SQL query to avoid the error. 如果在查询中同时使用了 ARGMAX_AGG 和 DISTINCT，则会引发内部错误。此问题已解决。现在，这种情况会引发一条不受支持的错误消息，其中包含有关如何重新执行 SQL 查询以避免错误的提示。
VER-91425	FlexTable	The copy of multiple json files to Vertica table using fjsonparser() is successful now, which was causing the initiator node down issue before this fix. 现在，使用 fjsonparser() 将多个 json 文件复制到 Vertica 表已成功，这在修复之前会导致启动器节点关闭问题。
VER-91661	Execution Engine	If the bounds provided by table statistics are out of order (low bound > high bound) and one of the bounds is 0, division expression analysis can result in a crash. This is likely caused by bad data. This issue has been resolved. Now, integrity checks have been added so that if the bounds provided are out of order, a warning is reported and the out-of-order section of the table’s range is considered unbounded. 如果表统计信息提供的边界无序（低边界 > 高边界）并且其中一个边界为 0，则除法表达式分析可能会导致崩溃。这可能是由不良数据引起的。此问题已解决。现在，已添加完整性检查，因此如果提供的边界无序，则会报告警告，并且表范围的无序部分将被视为无界。
VER-91739	Installation: Server RPM/Deb	The vioperf on some RHEL9 machines would OOM (out-of-memory) if run. This issue has been resolved. 某些 RHEL9 计算机上的 vioperf 在运行时会出现 OOM（内存不足）现象。此问题已解决。
VER-91760	Installation Program	Previously, the {{install_vertica}} script would return an error if it was unable to determine the device ID, which occurred if any file under /sys/block/{}sd_dir{}/dev/ was missing. This has been fixed; {{install_vertica}} now skips missing dev files, if any. 以前，如果 {{install_vertica}} 脚本无法确定设备 ID，则会返回错误，如果 /sys/block/{}sd_dir{}/dev/ 下的任何文件丢失，就会出现这种情况。此问题已修复；{{install_vertica}} 现在会跳过丢失的 dev 文件（如果有）。
VER-92719	EON, S3	Previously, FIPS-enabled databases crashed when Vertica accessed an S3 bucket. This issue has been resolved. 以前，当 Vertica 访问 S3 存储桶时，启用 FIPS 的数据库会崩溃。此问题已解决。
VER-92780	Execution Engine	Whether LIKE ANY / ALL read strings as UTF8 character sequences or binary byte arrays depended on whether the collation of the current locale was binary, leading to incorrect results when reading multi-character UTF8 strings in binary-collated locales. This has been resolved. Now, LIKE ANY / ALL always reads UTF8 character sequences, regardless of the current locale’s collation. LIKE ANY / ALL 是否将字符串读取为 UTF8 字符序列或二进制字节数组取决于当前语言环境的排序规则是否为二进制，这导致在二进制排序语言环境中读取多字符 UTF8 字符串时出现错误结果。此问题已解决。现在，LIKE ANY / ALL 始终读取 UTF8 字符序列，而不管当前语言环境的排序规则如何。
VER-92996	ComplexTypes, Kafka Integration	Loading JSON/Avro data with Kafka and Flex parsers into tables with many columns suffered from performance degradation. The performance issue has been resolved. 使用 Kafka 和 Flex 解析器将 JSON/Avro 数据加载到具有许多列的表中会导致性能下降。此性能问题已解决。
VER-93119	Backup/DR	LocalStorageLocator did not implement the construct_new() method. When called, it fell back to the StorageLocation.construct_new() method, which raised an error. This issue has been resolved. LocalStorageLocator.construct_new() is now implemented. LocalStorageLocator 未实现 constrain_new() 方法。调用时，它会回退到 StorageLocation.construct_new() 方法，从而引发错误。此问题已解决。现已实现 LocalStorageLocator.construct_new()。
VER-93162	Kubernetes	A new container was published that had the security vulnerabilities resolved. The container can be found at this public repository: opentext/vertica-logger:1.0.1 已发布一个已解决安全漏洞的新容器。可在此公共存储库中找到该容器：opentext/vertica-logger:1.0.1
VER-93339	Client Drivers - JDBC	Previously, the JDBC driver used the com.google.gson package as packaged by the original maven build. Now the classes have been shaded under com.vertica to avoid collisions with other versions of gson packages used. 以前，JDBC 驱动程序使用原始 maven 构建打包的 com.google.gson 包。现在，这些类已在 com.vertica 下着色，以避免与使用的其他版本的 gson 包发生冲突。
VER-93452	Kafka Integration	There’s now a better log message for incompatible compression types. 现在针对不兼容的压缩类型有更好的日志消息。
VER-93531	Client Drivers - ODBC	The Windows DSN configuration utility no longer sets vertica as the default KerberosServiceName value when editing a DSN. Starting with version 11.1, providing a value causes the ODBC driver to assume the connection is using Kerberos authentication and communicates to the server that it prefers to use that authentication method, assuming that the user has a grant to a Kerberos authentication method. The KerberosServiceName value might be set in earlier versions of Windows ODBC DSNs. Clearing the value will resolve the issue. This issue only applies to users who have a Kerberos authentication method granted with a lower priority than other authentication methods and use the DSN configuration utility to set up a DSN on Windows. 编辑 DSN 时，Windows DSN 配置实用程序不再将 vertica 设置为默认的 KerberosServiceName 值。从版本 11.1 开始，提供一个值会导致 ODBC 驱动程序假定连接正在使用 Kerberos 身份验证，并向服务器传达它更喜欢使用该身份验证方法的信息，假定用户已获得 Kerberos 身份验证方法的授权。KerberosServiceName 值可能在早期版本的 Windows ODBC DSN 中设置。清除该值将解决该问题。此问题仅适用于具有比其他身份验证方法优先级更低的 Kerberos 身份验证方法并使用 DSN 配置实用程序在 Windows 上设置 DSN 的用户。
VER-93656	Catalog Engine	Removed noisy transaction distcall slow events, which could cause all transactions to be blocked when system bottleneck occurs. 删除了嘈杂的事务 distcall 慢速事件，当系统出现瓶颈时，这些事件可能会导致所有事务被阻止。
VER-93773	Data load / COPY	In rare cases, copying a JSON to a table using FJsonParser or KafkaJsonParser could cause the server to go down. This issue has been resolved. 在极少数情况下，使用 FJsonParser 或 KafkaJsonParser 将 JSON 复制到表可能会导致服务器关闭。此问题已解决。
VER-93774	UI - Management Console	There is an issue with bad clusters in Management Console. This issue has been resolved. Now, the derby data is refreshed and the database is removed and again imported into Management Console. 管理控制台中存在坏集群问题。此问题已解决。现在，derby 数据已刷新，数据库已删除并再次导入管理控制台。
VER-93809	Catalog Engine	Improvements to mutex profiling have been added. 增加了对互斥分析的改进。
VER-93972	Optimizer	When a table was queried with sampling, partition pruning was blocked because the system attempted to simultaneously reason about the original predicates and the random sampling predicate. This issue has been resolved. Now, expression analysis on the original predicates is done separately from the random sampling predicate. 当使用抽样查询表时，分区修剪被阻止，因为系统试图同时推理原始谓词和随机抽样谓词。此问题已解决。现在，对原始谓词的表达式分析与随机抽样谓词分开进行。
VER-94024	Catalog Engine	As dc_catalog_refcounts is useful only for debugging purposes, it is disabled by default. 由于 dc_catalog_refcounts 仅用于调试目的，因此默认情况下它是禁用的。
VER-94030	Basics	Setting SlowEventsProfilingFreq to 0 caused a cluster failure. This issue has been resolved. 将 SlowEventsProfilingFreq 设置为 0 会导致集群故障。此问题已解决。
VER-94039	Data load / COPY	Vertica is now handling the null file and a null found case outside the json object with fjsonparser. Vertica 现在使用 fjsonparser 处理 json 对象之外的空文件和空发现情况。
VER-94082	Depot	Depot fetch used to call AWS list request, but now doesn’t. Depot fetch 过去用于调用 AWS 列表请求，但现在不会。
VER-94118	Kafka Integration	The vkconfig --refresh-interval option now functions properly. Setting it to one hour will refresh the lane worker every hour. vkconfig --refresh-interval 选项现在正常运行。将其设置为一小时将每小时刷新一次通道工作者。
VER-94158	Depot	The subcluster-level depot pin policy became the cluster-level policy after upgrading to version 23.4 or later. This issue has been resolved. For users already using version 23.4 or later, subcluster-level depot policies must be recreated. 升级到 23.4 或更高版本后，子集群级仓库固定策略变为集群级策略。此问题已解决。对于已经使用 23.4 或更高版本的用户，必须重新创建子集群级仓库策略。
VER-95476	Tuple Mover	After performing a reshard database, the Tuple Mover logged a large number of PURGE requests on a projection while resharded containers exist on that projection. This issue has been resolved. 执行重新分片数据库后，Tuple Mover 在投影上记录了大量 PURGE 请求，而该投影上存在重新分片的容器。此问题已解决。