24.3.x Resolved issues¶
24.3.0-15¶
Updated 05/29/2026
| Issue Key | Component | Description |
|---|---|---|
| 5332447 | Execution Engine | Previously, float division evaluation would produce an INFO line of log output to note the inputs and outputs of the operation. This output was extraneous and caused rapid log file growth that scaled linearly with the number of rows processed for certain queries. Now this log output has been removed. 修复了浮点除法运算产生大量 INFO 日志输出的问题。此前每次浮点除法都会输出一行 INFO 日志，导致日志文件随处理行数线性增长，现已移除此多余日志。 |
| 5381294 | UI - Management Console | This update addresses a critical security vulnerability, CVE-2025-12453, identified as a Reflected Cross-Site Scripting (XSS) flaw in Vertica, specifically affecting version 10.0.1. Prior to this fix, an authenticated attacker could exploit unmanaged input parameters in certain Web UI endpoints to inject and execute arbitrary JavaScript code. This update includes essential security enhancements to mitigate the identified XSS vulnerability and measures to ensure proper sanitization and neutralization of user-supplied input, preventing the execution of malicious scripts. Users are advised to update to the latest version to benefit from these security improvements. 修复了严重安全漏洞 CVE-2025-12453（反射型 XSS），经过身份验证的攻击者可能利用 Web UI 端点中未处理的输入参数注入并执行任意 JavaScript 代码。此更新增强了输入净化和安全加固措施。 |
| 5393051 | Security | This update addresses a critical security vulnerability, identified as CVE-2026-33186, that was discovered within the gRPC dependency utilized by the Vertica database server. 修复了 Vertica 数据库服务器使用的 gRPC 依赖中的严重安全漏洞 CVE-2026-33186。 |
| 5395158 | UI - Management Console | This update includes an important security update to address CVE-2025-12454, fixing a vulnerability where certain cookies were not configured with the HTTPOnly flag. To mitigate potential risks associated with client-side script access to cookies, the application has been updated to set the HTTPOnly flag for critical session cookies. This flag prevents web browsers from allowing client-side scripts (such as JavaScript) to read or manipulate these cookies, thereby reducing the attack surface for session hijacking and cross-site scripting (XSS) vulnerabilities. 修复了 CVE-2025-12454 安全漏洞，关键会话 Cookie 现在设置 HTTPOnly 标志，阻止客户端脚本（如 JavaScript）读取或操作这些 Cookie，降低会话劫持和 XSS 攻击风险。 |
24.3.0-14¶
Updated 04/27/2026
| Issue Key | Component | Description |
|---|---|---|
| 5332813 | Backup/DR | Improved Snapshot Loading Performance with optimizations for load_snapshot() operation, addressing delays up to 4 hours on certain nodes. 优化了 load_snapshot() 操作的快照加载性能，解决了某些节点上长达 4 小时的延迟。 |
| 5301686 | Admin Tools | Resolves critical and high-severity security vulnerabilities discovered in version 23.4.0-23. 修复了 23.4.0-23 中发现的关键和高严重性安全漏洞。 |
| 5333792 | Backup/DR | Tombstone objects can have empty locations if queued after upgrade from 23.4 and older. Now uses default storage location. 修复了从 23.4 及更早版本升级后墓碑对象可能出现空位置的问题。 |
| 5355110 | Vcluster | Fixed vcluster add_subcluster failure with absolute catalog paths. 修复了 vcluster add_subcluster 在使用绝对目录路径时失败的问题。 |
24.3.0-13¶
Updated 03/20/2026
| Issue Key | Component | Description |
|---|---|---|
| 5203748 | Kafka Integration | Upgraded Log4j core library to version 2.25.3 to address CVE-2025-68161. 修复了 Log4j 核心库的安全漏洞 CVE-2025-68161，升级至 2.25.3。 |
| 5288077 | Data load / COPY | Fixed FCSVPARSER CRLF record terminator parsing issue causing data rejection. 修复了 FCSVPARSER 对 CRLF 记录终止符的解析错误导致数据被拒绝的问题。 |
24.3.0-12¶
Updated 02/27/2026
| Issue Key | Component | Description |
|---|---|---|
| 4988581 | Execution Engine | Fixed node crash from VAssert failure related to memory allocation. 修复了内存分配相关的 VAssert 失败导致的节点崩溃问题。 |
| 5008395 | Execution Engine | Fixed complex queries using internal temp relations that could error or output duplicate rows. 修复了使用内部临时关系的复杂查询可能报错或输出重复行的问题。 |
| 5014868 | Catalog Engine | Fixed node crash during ALTER TABLE from TieredCatalog VAssert error. 修复了执行 ALTER TABLE 时 TieredCatalog 组件 VAssert 错误导致的节点崩溃。 |
| 5086373 | Data Networking | Addressed potential deadlock from TS callback destructors executing while holding a lock. 解决了 TS 回调析构器在持有锁时执行可能导致死锁的问题。 |
| 5087107 | Data Networking | Fixed database hang after upgrade when MinTLSVersion set to 3. 修复了升级后 MinTLSVersion 设为 3 时数据库挂起的问题。 |
| 5108703 | System: Performance | Fixed scan column tracking for resharded databases. 修复了重分片数据库中扫描列的跟踪方式。 |
| 5191582 | Admin Tools | AdminTools restart_node now consistently finds primary UP node for catalog editor. AdminTools restart_node 现在始终使用 PRIMARY UP 节点运行目录编辑器。 |
24.3.0-11¶
Updated 01/13/2026
| Issue Key | Component | Description |
|---|---|---|
| 4561940 | UI - Management Console | Fixed DBD upload file permission error. 修复了 MC 中 DBD 上传文件权限错误。 |
| 4856055 | Machine Learning | Fixed VIAssert failure when importing XGBoost PMML models. 修复了导入 PMML 格式 XGBoost 模型时触发的 VIAssert 失败。 |
| 4880318 | System: Performance | Fixed STRPOS with GROUP BY causing 100% CPU on large datasets. 修复了 STRPOS 函数在大型数据集上 GROUP BY 时导致 CPU 100% 的问题。 |
| 4892655 | Machine Learning | Fixed TensorFlow model import requiring wrong number of input columns. 修复了导入 TensorFlow 模型时需要错误数量输入列的问题。 |
| 4937246 | QA - MC | Fixed MC extended monitoring not streaming data. 修复了 MC 扩展监控无法流式传输数据的问题。 |
| 4986857 | Kafka Integration | Upgraded librdkafka from 0.11.6 to 2.4.0 for improved compatibility. 将 librdkafka 从 0.11.6 升级到 2.4.0，提高 Kafka 客户端兼容性。 |
| 5005745 | EON | Fixed cluster node crashes from memory leak causing OOM errors. 修复了集群节点因内存泄漏导致 OOM 频繁崩溃的问题。 |
| 5008272 | Optimizer | Fixed crash when comparing string array literals with LIKE ANY/ALL. 修复了字符串数组与 LIKE ANY/ALL 比较时导致崩溃的问题。 |
| 5011526 | Security | Introduced OAuth2JITConflictPolicy parameter for OAuth2 JIT login control. 新增数据库参数 OAuth2JITConflictPolicy，控制 OAuth2 JIT 登录。 |
| 5050394 | Admin Tools | Fixed upgrade process and FlexTableLib library handling. 修复了升级过程和 FlexTableLib 库处理问题。 |
| 5059332 | Cloud - Amazon | Fixed Cluster Truncation Lag from ExpiredToken errors in S3. 修复了 S3 中 ExpiredToken 错误导致的集群截断延迟问题。 |
| 5078586 | Execution Engine | Fixed replicated tables error in cross-namespace ILM operations. 修复了跨命名空间 ILM 操作中复制表报错的问题。 |
| 5081952 | Backup/DR | Fixed server-based replication failure after EE to Eon migration. 修复了 EE 迁移到 Eon 模式后基于服务器的复制失败问题。 |
| 5093601 | Backup/DR | Fixed Int-String comparison in VBR restore. 修复了表表达式中 Int-String 比较导致 VBR 恢复失败的问题。 |
| 5114677 | Execution Engine | Fixed secondary subcluster PANIC errors from complex SELECT queries. 修复了复杂 SELECT 查询导致辅助子集群 PANIC 错误的问题。 |
24.3.0-10¶
Updated 09/26/2025
| Issue Key | Component | Description |
|---|---|---|
| 4350103 | Documentation | Updated SMTP email alert documentation for current Email gateway settings. 更新了 SMTP 邮件告警文档以反映当前的 Email 网关设置。 |
| 4450260 | Complex Types | Fixed EXPLODE/UNNEST error with non-binary collation locale. 修复了非二进制排序规则区域设置中 EXPLODE/UNNEST 的错误。 |
| 4950426 | Data load / COPY | Fixed node down from CopyFaultTolerantExpressions with TO_CHAR conversions. 修复了 CopyFaultTolerantExpressions 与 TO_CHAR 转换同时使用时节点宕机的问题。 |
| 4965951 | Third Party Tools Integration | Addressed critical security vulnerabilities CVE-2024-24790, CVE-2024-45338, CVE-2024-45337. 修复了第三方工具集成中的关键安全漏洞 CVE-2024-24790 等。 |
| 4980285 | Node Management Agent, Vcluster | Addressed critical security vulnerabilities in Go binaries by upgrading compiler and libraries. 通过升级 Go 编译器和库修复了 Go 二进制文件中的关键安全漏洞。 |
24.3.0-9¶
Updated 08/07/2025
| Issue Key | Component | Description |
|---|---|---|
| 4535434 | License | Removed spurious "Skipping node information" warnings from error_messages table. 移除了 error_messages 表中无意义的 'Skipping node information' 警告。 |
| 4639072 | Optimizer | Statistics histogram invalidation no longer occurs without full reanalysis. 修复了行计数更新后统计信息直方图失效的问题。 |
| 4646995 | Installation Program | install_vertica can generate self-signed certificates for openSSL >=3.2.2. install_vertica 现在可为 openSSL >=3.2.2 生成自签名证书。 |
| 4771993 | License | Fixed license audit compliance status anomaly. 修复了许可证审计合规状态显示异常的问题。 |
| 4811712 | Execution Engine | Fixed JSON escape character parsing issue causing missing characters. 修复了大型 JSON 文件中转义字符导致解析字符串缺少字符的问题。 |
| 4821849 | Data Load / COPY | Fixed node crash with inconsistent JSON ARRAY column values during COPY. 修复了不一致的 JSON ARRAY 列值导致 COPY 时节点崩溃的问题。 |
| 4871603 | UI - Management Console | Fixed SMTP configuration without authentication not supported. 修复了不支持无认证 SMTP 配置的问题。 |
24.3.0-8¶
Updated 04/01/2025
| Issue Key | Component | Description |
|---|---|---|
| 4537046 | Database Designer Core, Refresh | Fixed historical query blocking at epochs prior to Ancient History Mark during Refresh. 修复了 Refresh 命令期间历史查询在 Ancient History Mark 之前被阻塞的问题。 |
24.3.0-7¶
Updated 03/24/2025
| Issue Key | Component | Description |
|---|---|---|
| 4391365 | DDL - Table | Fixed reference_schema_id invalidation in vs_view_tables after upgrade from 23.4. 修复了从 23.4 升级后 vs_view_tables 中 reference_schema_id 失效的问题。 |
| 4404830 | Scrutinize, Vcluster | Vcluster scrutinize now includes column headers in retrieved files. Vcluster scrutinize 现在在检索的文件中包含列标题。 |
| 4447927 | Admin Tools, Backup/DR | Added IMDSv2 support for config setup at db start. 数据库启动时增加了 IMDSv2 支持。 |
| 4524708 | EON | UsePeerToPeerDataTransfer parameter can be set at subcluster level. UsePeerToPeerDataTransfer 参数现在可在子集群级别设置。 |
| 4534860 | Catalog Engine, Tuple Mover | Fixed performance degradation after upgrade from 12.0.4 to 24.3/24.4. 修复了从 12.0.4 升级到 24.3/24.4 后的性能下降问题。 |
24.3.0-6¶
Updated 03/20/2025
| Issue Key | Component | Description |
|---|---|---|
| 4348794 | Directed Query | Fixed directed query search matching for CONST op CONST predicates. 修复了 CONST op CONST 谓词时定向查询无法匹配的问题。 |
| 4348813 | Execution Engine | Fixed priority field not persisting in catalog across restarts. 修复了 priority 字段在数据库重启后未持久化的问题。 |
| 4350035 | Data load / COPY | Fixed wildcard expansion in COPY on systems with certain GLIBC versions. 修复了特定 GLIBC 版本上 COPY 通配符扩展失败的问题。 |
| 4350068 | HTTP | Vertica Embedded HTTPS service now enforces HSTS header. Vertica 嵌入式 HTTPS 服务现在强制执行 HSTS 头。 |
| 4350124 | Documentation | Removed unnecessary R language pack restrictions from Supported Platforms. 从 Supported Platforms 中移除了不必要的 R 语言包限制说明。 |
| 4392280 | UDX | Fixed Python UDx with DEPENDS clause for Azure/GCS storage. maxNest increased to 15. 修复了 Python UDx 中 Azure/GCS 依赖库的 DEPENDS 子句问题，maxNest 增至 15。 |
| 4392304 | Optimizer | Fixed partition statistics replacing full table statistics causing suboptimal plans. 修复了分区统计信息替代全表统计信息导致计划不理想的问题。 |
| 4392306 | Data load / COPY | Performance improvement for EXECUTE DATA LOADER WITH FILES with large file counts. 优化了 EXECUTE DATA LOADER WITH FILES 在大量文件时的性能。 |
| 4276319 | Optimizer | Partition statistics can now be collected on single-direction unbounded ranges. 分区统计信息现在可以收集单向无界范围的数据。 |
24.3.0-5¶
Updated 12/29/2024
| Issue Key | Component | Description |
|---|---|---|
| 4347935 | UI - Management Console | Fixed MC v12.0 Query Profile page localization issue. 修复了 MC v12.0 本地化后查询配置文件页面未翻译的问题。 |
| 4347720 | Performance tests | Vnetperf utility now compatible with RHEL9 and Python3. Vnetperf 工具现在兼容 RHEL9 和 Python3。 |
| 4348680 | EON | Fixed potential FNF/leaked files in restore/replicate. 修复了恢复/复制中可能的文件未找到或文件泄露问题。 |
| 4348804 | Execution Engine | Fixed FCSVParser core dump with glob pattern file loading. 修复了使用 glob 模式加载多个文件时 FCSVParser 核心转储的问题。 |
| 4349211 | License | Fixed automated database size audit timing issue. 修复了自动数据库大小审计时间与 GET_AUDIT_TIME 不一致的问题。 |
| 4350010 | Backup/DR | Fixed show-restore-points path canonicalization for bucket root paths. 修复了 show-restore-points 路径规范化问题。 |
| 4350657 | Installation Program | Fixed installation on Amazon 2023 Linux. 修复了在 Amazon 2023 Linux 上安装失败的问题。 |
| 4358591 | UI - Management Console | Fixed potential cross-site scripting vulnerability. 修复了潜在的跨站脚本安全漏洞。 |
| 4392244 | Optimizer | Fixed WITH statements on multiple query levels with different target lists. 修复了多层 WITH 语句在不同目标列表时返回错误的问题。 |
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 请求，而该投影上存在重新分片的容器。 此问题已解决。 |