StarRocks/starrocks 3.3.21

on GitHub

Release Date: December 25, 2025

Bug Fixes

The following issues have been fixed:

• Logic errors when the trim function handles specific Unicode whitespace characters (for example, \u1680) and performance issues caused by reserved memory calculation. #66428 #66477
• Foreign key constraints are lost after FE restart due to table loading order. #66474
• Security vulnerabilities CVE-2025-66566 and CVE-2025-12183 in lz4-java, and potential crashes in upstream. #66453 #66362 #67075
• Incorrect results when Join is used with window functions in Group Execution mode. #66441
• System continues attempting to fetch metadata for a deleted warehouse, causing SHOW LOAD or SQL execution failures. #66436
• PartitionColumnMinMaxRewriteRule optimization incorrectly returns an empty set instead of NULL when the Scan input for aggregation is fully filtered. #66356
• Rowset IDs are not properly released when Rowset Commit or Compaction fails, preventing disk space reclamation. #66301
• Missing scan statistics (for example, scanned rows/bytes) in audit logs when a high-selectivity filter causes the Scan to end early (EOS). #66280
• BE continues to respond to heartbeats as Alive after entering the crash handling process (for example, SIGSEGV), causing the FE to continue dispatching queries and reporting errors #66212
• BE crash caused by multiple calls to set_collector of the Runtime Filter due to Local TopN pushdown optimization. #66199
• Load task failures caused by un-initialized rssid when column-mode Partial Update is used with Conditional Update. #66139
• Race condition when submitting drivers in Colocate Execution Group, leading to BE crashes. #66099
• MemoryScratchSinkOperator remains in a pending state and cannot be cancelled after RecordBatchQueue is closed (For example, triggered by SparkSQL Limit), causing queries to hang. #66041
• Use-after-free issue caused by a race condition when accessing _num_pipelines in the ExecutionGroup countdown logic. #65940
• Incorrect calculation logic for query error rate monitoring metrics (Internal/Analysis/Timeout error rate), resulting in negative values. #65891
• Null Pointer Exception (NPE) caused by unset ConnectContext when executing tasks as an LDAP user. #65843
• Performance issues where Filesystem Cache lookups for the same Key fail because object reference comparison is used instead of value comparison. #65823
• Tablet-related files are not correctly cleaned up after a snapshot load failure due to incorrect status variable checking. #65709
• Compression type and level configured in FE are not correctly propagated to BE or persisted during table creation or Schema Change, resulting in default compression settings. #65673
• COM_STMT_EXECUTE has no audit logs by default, and Profile information is incorrectly merged into the Prepare stage. #65448
• Delete Vector CRC32 check failures during cluster upgrade/downgrade scenarios due to version incompatibility. #65442
• BE crash caused by improper handling of Nullable properties when UnionConstSourceOperator merges Union to Values. #65429
• Concurrent load tasks fail during the Commit phase if the target tablet is dropped during an ALTER TABLE operation. #65396
• Inaccurate error log information when authentication fails due to incorrect context setting if users are switched in the HTTP SQL interface. #65371
• Statistics collection issues after INSERT OVERWRITE, including failure to collect statistics for temporary partitions and inaccurate row count statistics at transaction commit preventing collection trigger. #65327, #65298, #65225
• HttpConnectContext related to SQL is not released in TCP connection reuse scenarios because subsequent non-SQL HTTP requests overwrite the context. #65203
• Potential version loss caused by incomplete tablet loading when RocksDB iteration times out during BE startup metadata loading. #65146
• BE crash caused by out-of-bounds access when processing compression parameters in the percentile_approx_weighted function. #64838
• Missing Query Profile logs for queries forwarded from Follower to Leader. #64395
• BE crash caused by lax size checks during LZ4 encoding of large string columns during spilling. #61495
• MERGING-EXCHANGE operator crash caused by Ranking window function optimization generating an empty ORDER BY when there is no PARTITION BY and GROUP BY. #67081
• Unstable results or errors in the Low Cardinality column rewrite logic due to dependence on the Set iteration order. #66724