24.1.0-8
Updated 10/24/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-95963 | 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-96251 | 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-96387 | Backup/DR | VBR no longer requires compat-openssl11 to be installed on RHEL9 systems. VBR 不再需要在 RHEL9 系统上安装 compat-openssl11。 |
| VER-96872 | Security | Clients not sending packets during initialization of TLS connections will no longer cause CPU usage to spike. 在 TLS 连接初始化期间不发送数据包的客户端将不再导致 CPU 使用率飙升。 |
| VER-97036 | 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-97118 | UI - Management Console | In MC v11.0, the Query Profile page was working without any issues. MC v12.0 was localized and all labels were translated. However, the Query Profile page was not localized by oversight. This issue has been resolved. 在 MC v11.0 中，查询配置文件页面运行正常。MC v12.0 已本地化，所有标签都已翻译。但是，由于疏忽，查询配置文件页面未本地化。此问题已解决。 |
| VER-97235 | Data load / COPY | Previously, when querying certain ORC/Parquet files in a certain way, a hang would occur. This issue has been resolved. 以前，以某种方式查询某些 ORC/Parquet 文件时会出现挂起。此问题已得到解决。 |
| VER-97340 | 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-97491 | Execution Engine | When converting strings to numeric using the binary scale notation, using some very large powers would cause internal calculations to overflow, bypass some syntax checks, and crash. This issue has been resolved; the syntax checks now account for those large powers. 使用二进制表示法将字符串转换为数字时，使用一些非常大的幂会导致内部计算溢出、绕过一些语法检查并崩溃。此问题已解决；语法检查现在会考虑这些大幂。 |
24.1.0-7
Updated 08/29/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-96127 | 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.1.0-6
Updated 08/22/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-92427 | UI - Management Console | On RedHat 8, clients will use systemctl to start/stop the Management Console. RedHat 8’s default timeout to start an application is 90s; this default timeout might not be long enough. With this fix, the timeout is now set to 5 minutes. 在 RedHat 8 上，客户端将使用 systemctl 来启动/停止管理控制台。 RedHat 8 启动应用程序的默认超时时间为 90 秒； 此默认超时时间可能不够长。 通过此修复，超时现在设置为 5 分钟。 |
| VER-92924 | UI - Management Console | Previously, upgrading the Management Console from version 12.0.4 to 23.3.0 could cause LDAP users to be incorrectly migrated, preventing users from logging in. This issue has been resolved. 以前，将管理控制台从版本 12.0.4 升级到 23.3.0 可能会导致 LDAP 用户被错误迁移，从而阻止用户登录。 此问题已解决。 |
| VER-94143 | Client Drivers - JDBC | Previously, the JDBC driver used the com.google.gson package that was available in the original maven build. The classes are now shaded under com.vertica to avoid conflict with other versions of gson packages used. 以前，JDBC 驱动程序使用原始 maven 构建中提供的 com.google.gson 包。 这些类现在在 com.vertica 下进行遮蔽，以避免与使用的其他版本的 gson 包发生冲突。 |
| VER-94205 | 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-94570 | 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-94596 | 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-95104 | 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-95109 | 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-95249 | 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. The issue has been resolved. 使用派生表达式对投影进行 FKPK 连接会将 PK 输入放在内侧，即使它比 FK 输入大得多，这在某些情况下会导致性能下降。 此问题已解决。 |
| VER-95550 | Execution Engine | An issue that caused a crash while using WITHIN GROUP () function with listagg has been fixed. 已修复使用 WITHIN GROUP () 函数与 listagg 时导致崩溃的问题。 |
| VER-95662 | 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 运算符求值时会得到错误的结果。 此问题已解决。 |
| VER-95820 | 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 error has been resolved. REGEXP_SUBSTR 表达式分析中的错误有时会导致该函数处于连接条件时崩溃。 此错误已解决。 |
24.1.0-5
Updated 05/29/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-93445 | 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-93610 | 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.以前，如果无法确定设备 ID， install_vertica 脚本会返回错误，如果 /sys/block/sd_dir/dev/ 下的任何文件丢失，就会发生这种情况。此问题已修复；install_vertica 现在会跳过丢失的 dev 文件（如果有）。 |
| VER-93924 | 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-93931 | 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-94332 | 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-94401 | Installation: Server RPM/Deb | On some RHEL9 machines, the vioperf utility would OOM (out-of-memory) if run. This issue has been fixed. 在某些 RHEL9 机器上，运行 vioperf 实用程序时会出现 OOM（内存不足）现象。 此问题已修复。 |
24.1.0-4
Updated 04/18/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-91666 | ResourceManager | If the default resource pool, defined by the DefaultResourcePoolForUsers configuration parameter, was set to a value other than ‘general’, the user’s view incorrectly reported the non-general resource pool as the default pool when the user didn’t have that non-general pool set in the profile. This issue has been resolved. The default pool in such cases is now correctly reported as ‘general’. 如果将 DefaultResourcePoolForUsers 配置参数定义的默认资源池设置为“general”以外的值， 则当用户未在配置文件中设置非通用资源池时，用户的视图会错误地将非通用资源池报告为默认池。 此问题已解决。在这种情况下，默认池现在会正确报告为“general”。 |
| VER-92112 | Catalog Engine | Previously, syslog notifiers could cause the node to go down when attached to certain DC tables. This issue has been resolved. 以前，系统日志通知程序在连接到某些 DC 表时可能会导致节点关闭。此问题已解决。 |
| VER-92286 | Sessions | The ALTER USER statement could not set the idle timeout for a user to the default value, which is defined by the DefaultIdleSessionTimeout configuration parameter. If the empty string was specified, the idle timeout was set to unlimited. T his issue has been resolved. You can now set the idle timeout to the DefaultIdleSessionTimeout value by specifying ‘default’ in the ALTER USER statement. ALTER USER 语句无法将用户的空闲超时设置为默认值，该默认值由 DefaultIdleSessionTimeout 配置参数定义。 如果指定了空字符串，则空闲超时将设置为无限制。 此问题已解决。 现在，您可以通过在 ALTER USER 语句中指定“default”将空闲超时设置为 DefaultIdleSessionTimeout 值。 |
| VER-92534 | Data load / COPY | When the Avro parser would read a byte array that is at most 8 bytes long into a numeric-typed target, it would only accept a single-word numeric as the target type. This has been resolved; now, the Avro parser supports reading short byte arrays into multi-word numeric targets. 当 Avro 解析器将最多 8 个字节长的字节数组读入数字类型目标时，它只接受单词数字作为目标类型。 此问题已得到解决；现在，Avro 解析器支持将短字节数组读入多字数字目标。 |
| VER-92662 | Scrutinize | The scrutinize utility produces a tarball of the data it collects. Previously, scrutinize could fail to create this tarball if it encountered a broken symbolic link. This has been fixed, and the size of the tarball is now logged to scrutinize_collection.log.scrutinize 实用程序会生成其收集的数据的 tarball。 以前，如果 scrutinize 遇到损坏的符号链接，则可能无法创建此 tarball。 此问题已得到修复，tarball 的大小现在记录到“scrutinize_collection.log”中。 |
| VER-92747 | HTTP | Changing the Vertica server certificate triggers an automatic restart of the built-in HTTPS server. When this happened on a busy system, the nodes could sometimes go down. The issue has been fixed. 更改 Vertica 服务器证书会触发内置 HTTPS 服务器的自动重启。 当这种情况发生在繁忙的系统上时，节点有时会关闭。 此问题已得到修复。 |
| VER-92819 | Data load / COPY | In COPY, some missing error checks made it so certain invalid input could crash the database. This has been resolved. 在 COPY 中，缺少一些错误检查，导致某些无效输入可能会导致数据库崩溃。 此问题已解决。 |
| VER-92926 | Installation Program | When you installed Vertica on RHEL 9 with the install_vertica script, there was a warning about a missing ] character. This issue has been resolved. 使用 install_vertica 脚本在 RHEL 9 上安装 Vertica 时，会出现有关缺少 ] 字符的警告。此问题已解决。 |
| VER-93250 | EON, S3 | Previously, FIPS-enabled databases crashed when Vertica accessed an S3 bucket. This issue has been resolved. 以前，当 Vertica 访问 S3 存储桶时，启用 FIPS 的数据库会崩溃。 此问题已解决。 |
| VER-93325 | Execution Engine | User-Defined Aggregates didn’t work with single distinct built-in aggregate in the same query when the input wasn’t sorted on grouping columns plus distinct aggregate column. The issue has been resolved. 当输入未按分组列和不同的聚合列排序时，用户定义聚合无法与同一查询中的单个不同的内置聚合一起使用。 此问题已解决。 |
| VER-93527 | 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 数据加载到具有许多列的表中会导致性能下降。 性能问题已解决。 |
24.1.0-3
Updated 03/13/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-91789 | Logging | The LogRotate metafunction and timer service now support dbLog files. LogRotate 元函数和计时器服务现在支持 dbLog 文件。 |
| VER-92164 | Procedural Languages | Previously, running certain types of queries inside a stored procedure could cause the database to go down. This issue has been resolved. 以前，在存储过程内运行某些类型的查询可能会导致数据库崩溃。 此问题已解决。 |
| VER-92577 | Data load / COPY | Previously Vertica had poor performance when loading wide tables using RecordParser that performs case-insensitive comparisons. This issue has been resolved. 以前，Vertica 在使用执行不区分大小写的比较的 RecordParser 加载宽表时性能不佳。 此问题已解决。 |
| VER-92609 | Execution Engine | When you executed a query that filtered data into a JOIN statement, the query processed incorrectly or returned an error. This issue has been resolved. 当您执行将数据过滤到 JOIN 语句中的查询时，查询处理不正确或返回错误。 此问题已解决。 |
24.1.0-2
Updated 02/27/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-91476 | Execution Engine | Since Version 11.1 SP1, in some cases, an optimization in the query plan caused queries running under Crunch Scaling mode of COMPUTE_OPTIMIZED to produce wrong results. This issue has been resolved. 自版本 11.1SP1 以来，在某些情况下，查询计划中的优化会导致在 COMPUTE_OPTIMIZED 的 Crunch Scaling 模式下运行的查询产生错误的结果。 此问题已解决。 |
| VER-91713 | Optimizer | Queries with identically looking predicates on different tables used in different subqueries where predicates have very different selectivity could result in bad query plans and worse performance due to incorrect estimates on those tables. The issue has been resolved. 如果查询在不同表上使用相同的谓词，而这些子查询中的谓词具有非常不同的选择性，则由于对这些表的估计不正确，可能会导致查询计划不佳和性能下降。 此问题已解决。 |
| VER-91741 | Execution Engine | The NULLIF function would infer its output type based on only the first argument. This led to type compatibility errors when the first argument was a small numeric type and the second argument was a much larger numeric type. This has been resolved; now, numeric NULLIF accounts for the types of both arguments when inferring its output type. NULLIF 函数将仅根据第一个参数推断其输出类型。 当第一个参数是较小的数字类型而第二个参数是较大的数字类型时，这会导致类型兼容性错误。 此问题已解决； 现在，数字 NULLIF 在推断其输出类型时会考虑两个参数的类型。 |
| VER-91792 | Execution Engine | In rare situations, a logic error in the execution engine “ABuffer” operator would lead to buffer overruns resulting in undefined behavior. This issue has been resolved. 在极少数情况下，执行引擎“ABuffer”运算符中的逻辑错误会导致缓冲区溢出，从而导致未定义的行为。 此问题已解决。 |
| VER-91817 | Execution Engine | Vertica’s execution engine pre-fetches data from disk to reduce wait time during query execution. Memory for the pre-fetch buffers was not reserved with the resource manager, and in some situations a pre-fetch buffer could grow to a large size and bloat the memory footprint of a query until it completed. Now queries will account for this pre-fetch memory in requests to the resource manager; and several internal changes mitigate the long-term memory footprint of larger-than-average pre-fetch buffers. Vertica 的执行引擎从磁盘预取数据以减少查询执行期间的等待时间。 资源管理器未保留预取缓冲区的内存，在某些情况下，预取缓冲区可能会增长到很大的大小并导致查询的内存占用膨胀，直到完成。 现在，查询将在对资源管理器的请求中考虑此预取内存； 并且一些内部更改减轻了大于平均值的预取缓冲区的长期内存占用。 |
| VER-91909 | Optimizer | When a node goes down in Eon mode, the buddy node that handles double duty did not adjust the resource calculation. Now, the behavior is consistent with the Enterprise mode node-down scenario. 当节点在 Eon 模式下关闭时，处理双重任务的伙伴节点不会调整资源计算。 现在，该行为与企业模式节点关闭场景一致。 |
| VER-91959 | Execution Engine | Queries using WITH clauses which refer to the temporary relation at least N times, where N is the value of the configuration parameter “EnableWITHTempRelReuseLimit”, could suddenly abort the entire Vertica process if an exception (such as running out of temp space) occurred while materializing the temporary relation. We have improved the exception handling of this routine to avoid suddenly crashing the entire process, returning a normal error back to the user when possible or at least handling a PANIC in the fall-back scenario. 使用 WITH 子句的查询引用临时关系至少 N 次， 其中 N 是配置参数“EnableWITHTempRelReuseLimit”的值，如果在实现临时关系时发生异常（例如临时空间不足）， 可能会突然中止整个 Vertica 进程。 我们改进了此例程的异常处理，以避免突然崩溃整个过程，在可能的情况下将正常错误返回给用户， 或者至少在回退场景中处理 PANIC。 |
| VER-92054 | Procedural Languages | Fixed memory leaks that could occur with certain stored procedures. 修复了某些存储过程可能发生的内存泄漏。 |
| VER-92108 | DDL - Projection | When we would scan over a projection sorted by two columns (ORDER BY a,b) and materialize only the second one in the sort order (b), we would mistakenly assume the scan is sorted by that column for the purposes of collecting column statistics. This would lead to possible incorrect results when predicate analysis is enabled, and has now been resolved. 当我们扫描按两列排序的投影（ORDER BY a,b）并仅按排序顺序（b）实现第二列时， 我们会错误地认为扫描按该列排序以收集列统计信息。 这可能会导致在启用谓词分析时出现不正确的结果，现在已解决。 |
| VER-92123 | Optimizer | Queries using the same views repeatedly would sometimes return errors if those views included WITH clauses. The issue has been resolved. 如果这些视图包含 WITH 子句，则重复使用相同视图的查询有时会返回错误。 该问题已解决。 |
24.1.0-1
Updated 01/25/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-91335 | Data Export | Previously, large (chunked) file uploads from Vertica to GCS (such as exports of Parquet to GCS) would fail if the uploaded files included a special character in their path. This issue has been resolved. 以前，如果上传文件的路径中包含特殊字符，从 Vertica 到 GCS 的大型（分块）文件上传（例如将 Parquet 导出到 GCS）将会失败。 此问题已解决。 |
| VER-91549 | Execution Engine | When a hash join on unique keys would spill, the value columns would sometimes have alignment issues between how the hash table was written and how it gets read by the spill code. If these value columns were string types, this could lead to a crash. This issue has been resolved. 当唯一键上的哈希连接发生溢出时，值列有时会在哈希表的写入方式和溢出代码的读取方式之间出现对齐问题。 如果这些值列是字符串类型，则可能会导致崩溃。 此问题已解决。 |
24.1.0-0
Updated 01/09/2024
| Issue Key | Component | Description |
|---|---|---|
| VER-28231 | Data load / COPY | Copy statement FILLER columns may now have the same name as table columns. Expressions referring to a column which has the same name between the table and the FILLER column set may be fully-qualified to resolve ambiguities with either the table name, or the special \*FILLER\* relation.复制语句 FILLER 列现在可能与表列同名。 引用表和 FILLER 列集之间同名的列的表达式可能完全合格，以解决表名或特殊 \*FILLER\* 关系的歧义。 |
| VER-80570 | 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-85618 | Optimizer | In version 10.1, Vertica updated its execution engine to sample execution times and selectivity of query predicates and join predicates to run them in the most efficient order. This has been disruptive to users who wrote queries which depended on a certain evaluation order, in particular that single-table predicates would be evaluated before join conditions. In particular, queries whose single-table predicates filter out data which would raise a coercion error at the join condition would sometimes raise an error after this change due to the join condition being evaluated first. Now, we improved this experience by ensuring that join conditions do not raise type coercion errors when they are evaluated before single-table predicates. 在 10.1 版本中，Vertica 更新了其执行引擎，以对查询谓词和连接谓词的执行时间和选择性进行抽样， 以便按最有效的顺序运行它们。 这对编写依赖于特定评估顺序的查询的用户造成了干扰，特别是单表谓词会在连接条件之前进行评估。 特别是，由于首先评估连接条件，其单表谓词过滤掉会在连接条件下引发强制错误的数据的查询有时会在更改后引发错误。 现在，我们通过确保在单表谓词之前评估连接条件时不会引发类型强制错误来改善这种体验。 |
| VER-86330 | UI - Management Console | The Vertica CloudFormation Templates (CFTs) available on the Amazon Web Services Marketplace were updated to enhance security. 已更新 Amazon Web Services Marketplace 上提供的 Vertica CloudFormation 模板 (CFT) 以增强安全性。 |
| VER-86838 | Execution Engine | 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-87863 | Machine Learning | Because of legacy contingencies of the SEEDED_RANDOM function, the function is left as is, and a new DISTRIBUTED_SEEDED_RANDOM function is added that generates a correct distribution of pseudorandom numbers. As with SEEDED_RANDOM, the new function is not publicly documented and supported because it does not meet the general expectations of a seeded random function. 由于 SEEDED_RANDOM 函数的遗留意外情况，该函数保持原样，并添加了一个新的 DISTRIBUTED_SEEDED_RANDOM 函数来生成正确的伪随机数分布。 与 SEEDED_RANDOM 一样，新函数没有公开记录和支持，因为它不符合种子随机函数的一般期望。 |
| VER-88411 | Security | In cases of intermittent network connectivity to an LDAP server, Vertica will now retry bind operations. 如果与 LDAP 服务器的网络连接间歇性中断，Vertica 现在将重试绑定操作。 |
| VER-88467 | Client Drivers - VSQL | When you executed CREATE ROUTING RULE to create a workload routing rule for a subcluster that did not exist, the error message returned an incorrect object ID for the nonexistent subcluster. This issue has been resolved, and now the error message returns the subcluster name provided in the TO SUBCLUSTER clause. 当您执行 CREATE ROUTING RULE 来为不存在的子集群创建工作负载路由规则时，错误消息返回了不存在的子集群的错误对象 ID。 此问题已解决，现在错误消息返回 TO SUBCLUSTER 子句中提供的子集群名称。 |
| VER-88499 | Installation Program, Installation: Server RPM/Deb | The Vertica installer outputs hints with URLs to the Vertica documentation website to help users with the installation process. The URLs in the installer have been updated to reflect a change in the Vertica documentation URL format. Vertica 安装程序会将带有 URL 的提示输出到 Vertica 文档网站，以帮助用户完成安装过程。 安装程序中的 URL 已更新，以反映 Vertica 文档 URL 格式的更改。 |
| VER-88658 | 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-88985 | UI - Management Console | The HTTP Strict-Transport-Security (HSTS) response header was added to all MC responses. This header informs the browser that you should access the site through HTTPS only, and that the browser should automatically convert any HTTP connections to HTTPS. HTTP Strict-Transport-Security (HSTS) 响应标头已添加到所有 MC 响应中。此标头通知浏览器您应该仅通过 HTTPS 访问站点，并且浏览器应自动将任何 HTTP 连接转换为 HTTPS。 |
| VER-89103 | Data load / COPY | If a Parquet query or load were to be interrupted (such as by a LIMIT clause, exception during execution, or user cancellation) while the database has configuration parameter ParquetColumnReaderSize set to zero, then Vertica could crash. This issue has been resolved. 如果 Parquet 查询或加载被中断（例如被 LIMIT 子句、执行期间的异常或用户取消），而数据库的配置参数 ParquetColumnReaderSize 设置为零，则 Vertica 可能会崩溃。 这个问题已经解决。 |
| VER-89211 | Security | The following improvements have been made to LDAPLink: - LDAP synchronizations have been optimized and now are much faster for nested groups. - Query profiling now works with LDAP dryrun functions. LDAPLink 已做出以下改进： - LDAP 同步已优化，现在对于嵌套组来说速度更快。 - 查询分析现在可与 LDAP dryrun 函数配合使用。 |
| VER-89284 | Tuple Mover | When the node with the lowest OID became secondary (for example, during cluster demotion), there might have been an increased number of deadlocks and timeouts due to Data Manipulation Language (DML) statements and internal Tuple Mover tasks. This issue has been resolved. 当具有最低 OID 的节点成为次要节点时（例如，在集群降级期间）， 由于数据操作语言 (DML) 语句和内部 Tuple Mover 任务，死锁和超时的数量可能会增加。 此问题已解决。 |
| VER-89369 | EON, Execution Engine | A LIKE ANY or LIKE ALL expression with a non-constant pattern argument on the right-hand side of the expression sometimes resulted in a crash or incorrect internal error. This issue has been resolved. Now, this type of pattern argument results in a normal error. 表达式右侧带有非常量模式参数的 LIKE ANY 或 LIKE ALL 表达式有时会导致崩溃或不正确的内部错误。 此问题已解决。 现在，这种类型的模式参数会导致正常错误。 |
| VER-89447 | Optimizer | In some circumstances, a UNION query that grouped an expression that coerced a value to a common data type returned an error. This issue has been resolved. 在某些情况下，将强制将值转换为通用数据类型的表达式分组的 UNION 查询会返回错误。 此问题已解决。 |
| VER-89482 | UI - Management Console | Node.js has been upgraded to address the CVE-2023-32002 and CVE-2022-43548 security vulnerabilities. Node.js 已升级以解决 CVE-2023-32002 和 CVE-2022-43548 安全漏洞。 |
| VER-89508 | Execution Engine | When casting a negative numeric value to an integer and the result of that cast would be 0, then we would incorrectly get an “out of range” error. This has been resolved. 当将负数值转换为整数并且该转换的结果为 0 时，我们会错误地收到“超出范围”错误。 此问题已解决。 |
| VER-89530 | ComplexTypes, Data load / COPY | A logic gap in the source code could lead to an infinite loop while loading complex arrays with thousands of elements, causing the DML statement to never complete. This issue has been resolved. 源代码中的逻辑漏洞可能导致在加载具有数千个元素的复杂数组时出现无限循环， 从而导致 DML 语句永远无法完成。 此问题已解决。 |
| VER-89623 | Data load / COPY | Loading JSON arrays into table columns having different case for JSON key and table column used to fail in some cases. The issue has been fixed. 将 JSON 数组加载到具有不同大小写的 JSON 键和表列的表列中在某些情况下会失败。 此问题已解决。 |
| VER-89647 | Hadoop | Previously, ‘Get block locations’ events were missing from the dc_udfs_events table. This issue has been resolved. 以前，dc_udfs_events 表中缺少“获取块位置”事件。 此问题已解决。 |
| VER-89665 | Backup/DR | Backups to S3 object storage and Google Cloud Storage failed and returned a “Temp path” error. This issue has been resolved. 备份到 S3 对象存储和 Google Cloud Storage 失败并返回“临时路径”错误。 此问题已解决。 |
| VER-89684 | Scrutinize | The parameter --log-limit determines the maximum size of the vertica log that will be preserved when running scrutinize. The limit is applied to the vertica.log file on all nodes in the cluster. The default value changed from 1GB to unlimited. 参数 --log-limit 确定运行 scrutinize 时将保留的 vertica 日志的最大大小。 此限制适用于集群中所有节点上的 vertica.log 文件。 默认值从 1GB 更改为无限制。 |
| VER-89721 | 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 resolved. 以前，当配置比根 CA 证书和节点间 TLS 的客户端证书更长的证书链时，配置将成功应用， 但导致集群关闭。 此问题已得到解决。 |
| VER-89825 | Backup/DR | On HDFS, vbr tried to delete storage files from the wrong fan-out directory. This has been resolved by providing vbr with the correct fan out directory. 在 HDFS 上，vbr 尝试从错误的扇出目录中删除存储文件。 此问题已通过为 vbr 提供正确的扇出目录得到解决。 |
| VER-89874 | Catalog Engine | During load planning, the EnableWithTempRelReuseLimit configuration parameter was temporarily set to 1. This affected other sessions on the same node, and concurrent COPY commands might make this change permanent. This issue has been resolved. 在负载规划期间， EnableWithTempRelReuseLimit 配置参数临时设置为 1。这会影响同一节点上的其他会话，并且并发的 COPY 命令可能会使此更改永久生效。 此问题已得到解决。 |
| VER-89881 | Catalog Engine | ALTER SESSION no longer crashes the node when a user without USAGE privileges on the public schema sets a non-udparameter. 当没有公共架构上的 USAGE 权限的用户设置非 ud 参数时，ALTER SESSION 不再导致节点崩溃。 |
| VER-89933 | Catalog Engine | Queries now run correctly when the files of delete vectors are in different storage locations. 当删除向量的文件位于不同的存储位置时，查询现在可以正确运行。 |
| VER-90101 | SDK-Python | Due to the user’s specific environment settings, the pip package had problems installing matplotlib-3.5.3 on the user’s environment. There were no issues when installing newer versions of matplotlib. To avoid these install issues, install verticapy-1.0.0, which is compatible with the newer matplotlib versions. 由于用户的特定环境设置，pip 包在用户环境中安装 matplotlib-3.5.3 时出现问题。 安装较新版本的 matplotlib 时没有问题。 为了避免这些安装问题，请安装与较新版本的 matplotlib 兼容的 verticapy-1.0.0。 |
| VER-90115 | Scrutinize | Scrutinize no longer hangs when running “Command” tasks. 运行“命令”任务时，Scrutinize 不再挂起。 |
| VER-90145 | UI - Management Console | A custom alert was disabled if its query ran for more than 10 seconds. Now, the default timeout is 30 seconds. You can adjust this setting with the threshold_query.disable_time_out property in the /opt/vconsole/config/console.properties file.如果查询运行时间超过 10 秒，则自定义警报将被禁用。 现在，默认超时为 30 秒。 您可以使用 /opt/vconsole/config/console.properties 文件中的 threshold_query.disable_time_out 属性调整此设置。 |
| VER-90855 | Optimizer | Create Table As Select statements with repeated occurrences of now() and similar functions were inserting incorrect results into the target table. The issue has been resolved. 重复出现 now() 和类似函数的 Create Table As Select 语句会将错误的结果插入目标表。 此问题已解决。 |
| VER-91148 | Data load / COPY | The upgrade of the C++ AWS SDK in 12.0.2 caused Vertica to make repeated calls to the metadata server for IAM authentication, affecting performance when accessing S3. Vertica now resets the timestamp to prevent excessive pulling. 12.0.2 中的 C++ AWS SDK 升级导致 Vertica 重复调用元数据服务器进行 IAM 身份验证，影响访问 S3 时的性能。 Vertica 现在会重置时间戳以防止过度拉动。 |
最后修改时间：2024-11-04 09:36:17
「喜欢这篇文章，您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容，转载时必须标注文章的来源（墨天轮），文章链接，文章作者等基本信息，否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容，欢迎发送邮件至：contact@modb.pro进行举报，并提供相关证据，一经查实，墨天轮将立刻删除相关内容。
