Vertica 24.4.x BUG修复记录

# 24.4.0-0
_Updated 10/29/2024_

| Issue Key | Component | Description |
| --------- | ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| VER-60917 | Installation Program | When installing Vertica on a remote machine, the install would hang if the /etc/motd file contained a password entry. This issue has been fixed.<br>在远程计算机上安装 Vertica 时，如果 /etc/motd 文件包含密码条目，则安装将挂起。此问题已修复。 |
| VER-82831 | Installation Program | To prevent Vertica from running out of resources, the root user's max PID value default is changed during the Vertica install to 203816.<br>为了防止 Vertica 耗尽资源，在 Vertica 安装期间，root 用户的最大 PID 值默认更改为 203816。 |
| VER-84267 | 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. <br>This issue has been resolved.<br>使用派生表达式对投影进行 FKPK 连接会将 PK 输入放在内侧，即使它比 FK 输入大得多，这在某些情况下会导致性能下降。<br>此问题已解决。 |
| VER-88686 | Client Drivers - JDBC, Execution Engine | Batch update statements which run multiple query plans would keep in memory query plans from each statement in the batch until the entire batch completed.  <br>This memory bloat could cause the cluster to crash due to running out of memory.  <br>This issue has been fixed; now the query plan for each statement in the batch is freed upon completion of that statement.<br>运行多个查询计划的批量更新语句会将批处理中每个语句的查询计划保留在内存中，直到整个批处理完成。<br>这种内存膨胀可能会导致集群因内存不足而崩溃。<br>该问题已得到修复；现在，批处理中每个语句的查询计划都会在该语句完成后释放。 |
| VER-91515 | Security | install_vertica will no longer prefer the system openssl library to the one shipped with Vertica on non-fips systems. <br>If you would like to use the system openssl library, delete the openssl libraries located at /opt/vertica/lib.<br>install_vertica 将不再优先选择系统 openssl 库，而是选择非 fips 系统上 Vertica 附带的库。<br>如果您想要使用系统 openssl 库，请删除位于 /opt/vertica/lib 的 openssl 库。 |
| VER-93368 | Optimizer | Under certain circumstances, partition statistics could be used in place of full table statistics, leading to suboptimal plans. This issue has been resolved.<br>在某些情况下，分区统计信息可能会代替全表统计信息，从而导致计划不理想。此问题已解决。 |
| VER-94478 | AMI | The {{install_vertica}} command fails if Transparent Huge Pages (THP) are incorrectly configured. The function that automatically enables THP has been removed. <br>For on-premises installations, follow the steps here [https://docs.vertica.com/24.2.x/en/setup/set-up-on-premises/before-you-install/manually-configured-os-settings/] to manually configure OS settings and disable THP. <br>If THP is not disabled, {{install_vertica}} will return an error.<br>For installations where THP needs to remain enabled, add the parameter {{--failure-threshold NONE}} when running {{install_vertica}} to bypass this requirement and complete the installation.<br>如果透明大页面 (THP) 配置不正确，则 {{install_vertica}} 命令会失败。自动启用 THP 的功能已被删除。<br>对于本地安装，请按照此处 [https://docs.vertica.com/24.2.x/en/setup/set-up-on-premise/before-you-install/manually-configured-os-settings/] 的步骤手动配置操作系统设置并禁用 THP。<br>如果未禁用 THP，则 {{install_vertica}} 将返回错误。<br>对于需要保持 THP 启用的安装，请在运行 {{install_vertica}} 时添加参数 {{--failure-threshold NONE}} 以绕过此要求并完成安装。 |
| VER-94504 | Execution Engine | An issue that caused a crash while using WITHIN GROUP () function with listagg has been fixed.<br>已修复使用 WITHIN GROUP () 函数与 listagg 时导致崩溃的问题。 |
| VER-95014 | Backup/DR | VBR no longer requires compat-openssl11 to be installed on RHEL9 systems.<br>VBR 不再需要在 RHEL9 系统上安装 compat-openssl11。 |
| VER-95097 | 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. <br>This orphan blob could cause a crash if there was an attempt to train a model with the same name on the same session. <br>This issue has been resolved.<br>有一种特殊情况，即当取消 ML 模型的训练时，会话中可能会残留一个孤立 blob。<br>如果尝试在同一会话中训练同名模型，此孤立 blob 可能会导致崩溃。此问题已解决。 |
| VER-95199 | Optimizer | Under certain circumstances, partition statistics could be used in place of full table statistics, leading to suboptimal plans. <br>This issue has been resolved.<br>在某些情况下，分区统计信息可能会代替全表统计信息，从而导致计划不理想。此问题已解决。 |
| VER-95497 | 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. <br>This issue has been resolved.<br>由于数字除法代码中存在错误，用户在对某些精度较高的数值进行 mod 运算符求值时会得到错误的结果。<br>此问题已得到解决。 |
| VER-95651 | Kubernetes | If a database has a corrupted or outdated catalog (where some nodes do not have the latest catalog), it may not revive correctly in Kubernetes. <br>A workaround is available to recreate nodes with an outdated catalog.<br>如果数据库的目录已损坏或过期（某些节点没有最新目录），则可能无法在 Kubernetes 中正确恢复。<br>有一种解决方法是重新创建具有过期目录的节点。 |
| VER-95721 | Execution Engine | An error in expression analysis for REGEXP_SUBSTR would sometimes lead to a crash when that function was in the join condition. <br>This error has been resolved.<br>REGEXP_SUBSTR 表达式分析中的错误有时会导致该函数处于连接条件时崩溃。<br>此错误已解决。 |
| VER-95884 | Data Export | Vertica previously supported numeric precision up to 38 digits when writing to and reading from the Parquet format. <br>This precision limit has now been increased to 153 digits.<br>Vertica 以前在写入和读取 Parquet 格式时支持高达 38 位的数字精度。<br>此精度限制现已增加到 153 位。 |
| VER-95988 | Backup/DR | Server-based replication with target namespace used to fail due to namespace name case sensitivity. <br>This issue has been resolved.<br>由于命名空间名称区分大小写，基于服务器的与目标命名空间的复制过去常常会失败。<br>此问题已解决。 |
| VER-96152 | EON | Previously, in certain cases when a cancel occurred during Vertica uploads to the communal storage, the node would crash. <br>This issue has now been fixed.<br>以前，在某些情况下，当 Vertica 上传到公共存储期间发生取消时，节点会崩溃。<br>此问题现已修复。 |
| VER-96243 | Catalog Engine | Qualified schema names with namespaces have some restrictions, which led to instances of no results being returned. <br>This issue has been resolved. Note: This issue only occurred with displaying the system table.<br>带有命名空间的合格架构名称有一些限制，这导致不返回任何结果的情况。此问题已解决。<br>注意：此问题仅在显示系统表时发生。 |
| VER-96866 | Security | Clients not sending packets during initialization of TLS connections will no longer cause CPU usage to spike.<br>在 TLS 连接初始化期间不发送数据包的客户端将不再导致 CPU 使用率飙升。 |
| VER-96876 | Node Management Agent | When scaling down a cluster in kubernetes, the nodes fail to delete. <br>This issue has been fixed.<br>在 kubernetes 中缩减集群时，节点无法删除。此问题已修复。 |
| VER-97019 | Admin Tools, <br>Installation Program, <br>Installation: Server RPM/Deb | The urllib3 version is now upgraded from 1.26.18 to 1.26.19.<br>urllib3版本现已从1.26.18升级到1.26.19。 |
| VER-97022 | Optimizer | Between v12 and v24, a previous bug fix made it so that null rows passed hash SIP filters. <br>This led to a performance drop on queries that relied on SIPS to filter out nulls early. <br>This has been resolved; now, SIP filters remove null rows again.<br>在 v12 和 v24 之间，之前的一个错误修复使得空行能够通过哈希 SIP 过滤器。<br>这导致依赖 SIPS 尽早过滤掉空值的查询性能下降。这个问题已经解决；<br>现在，SIP 过滤器再次删除了空行。 |
| VER-97047 | Kubernetes | If a customer has a database with multiple local storage locations (e.g. multiple DATA paths) that don't have a common path, they cannot revive the database in K8s. <br>This issue has been resolved by removing this limitation in K8s.<br>如果客户的数据库有多个本地存储位置（例如多个数据路径），但没有通用路径，则他们无法在 K8s 中恢复数据库。<br>此问题已通过在 K8s 中移除此限制得到解决。 |