Project: StarRocks (App Definition and Development / Database)
File: release-2.5.md

displayed_sidebar: "English" Release date: May 15, 2024 Optimized the usage of database locks for materialized view refresh to prevent deadlock. Both `s3a://` and `s3://` can be used to access data in AWS S3. Fixed the following issues: Schema change may cause issues in prefix index sorting, leading to incorrect results for queries based on prefix indexes. After a Routine Load task is paused due to Kafka cluster abnormalities, the background still attempts to connect to this abnormal Kafka cluster, which prevents other Routine Load tasks in this StarRocks cluster from consuming normal Kafka messages. When querying views in `information_schema`, the database lock is held for an unexpectedly long time, which prolongs the overall query time. Enabling Query Cache may cause BEs to crash if the SQL query contains a HAVING clause. This issue can be resolved by disabling Query Cache using `set enablequerycache=false`. When Query Cache is enabled, some queries may return an error message `All slotIds should be remapped`. Release date: March 22, 2024 `replaceifnotnull` supports BITMAP columns in an Aggregate table. Users can specify `replaceifnotnull` as the aggregate function for BITMAP columns in an Aggregate table. G1 Garbage Collector is used for JDK 9 and later by default. The default value of the BE parameter `updatecompactionsize_threshold` is changed from 256 MB to 64 MB to accelerate compaction. Fixed the following issues: Synchronizing data using StarRocks external tables encounters the error "commit and publish txn failed". The synchronization succeeds after a retry but the same copy of data is loaded twice. RPC transmit resources are temporarily unavailable due to GC issues. array_agg() in v2.5 processes NULLs in a different way than it does in v2.3. As a result, the query result is incorrect after an upgrade from v2.3 to v2.5. The Sink Operator in a query unexpectedly exits, which causes BEs to crash. Executing the DELETE command on an Aggregate table results in a race for accessing tablet metadata, which causes BEs to crash. The MemTracker encounters the Use-After-Free issue during UDF calling, which causes BEs to crash. The unnest() function does not support aliases. Release date: February 8, 2024 Added a pattern-matching function: . Added Bitmap value processing functions: serialize, deserialize, and serializeToString. Supports automatic activation of inactive materialized views when refreshing these materialized views. Optimized BE log printing to prevent too many irrelevant logs. Supports using to process and load Bitmap data into StarRocks and export Bitmap data from StarRocks to Hive. Added date formats `yyyy-MM-ddTHH:mm` and `yyyy-MM-dd HH:mm` to support TIMESTAMP partition fields in Apache Iceberg tables. Fixed the following issues: Running a Spark Load job that has no PROPERTIES specified causes null pointer exceptions (NPEs). INSERT INTO SELECT occasionally encounters the error "timeout by txn manager". The memory consumption of PageCache exceeds the threshold specified by the BE dynamic parameter `storagepagecache_limit` in certain circumstances. After a table is dropped and then re-created with the same table name, refreshing asynchronous materialized views created on that table fails. Writing data to S3 buckets using SELECT INTO occasionally encounters the error "The tablet write operation update metadata take a long time". Some operations during data loading may encounter "reached timeout". The DECIMAL type returned by SHOW CREATE TABLE is inconsistent with that specified in CREATE TABLE. If partition columns in external tables contain null values, queries against those tables will cause BEs to crash. When deleting data from a Duplicate Key table, if the condition in the WHERE clause of the DELETE statement has a leading space, the deleted data can still be queried using

Loading `array<string>` data from ORC files into StarRocks (`array<json>`) may cause BEs to crash. Querying Hive catalogs may be stuck and even expire. Partitions cannot be dynamically created if hour-level partitions are specified in the PARTITION BY clause. The error message "failed to call frontend service" is returned during loading from Apache Flink. Release date: Jan 10, 2024 Users can set or modify session variables when they or asynchronous materialized views. When using JDK, the default GC algorithm is G1. The result returned by the statement now includes the timestamps of consumption messages from each partition. Added the session variable `enablematerializedviewforinsert`, which controls whether materialized views rewrite the queries in INSERT INTO SELECT statements. The default value is `false`. Added the session variable `enablestrictorder_by`. When this variable is set to the default value `TRUE`, an error is reported for such a query pattern: Duplicate alias is used in different expressions of the query and this alias is also a sorting field in ORDER BY, for example, `select distinct t1.* from tbl1 t1 order by t1.k1;`. The logic is the same as that in v2.3 and earlier. When this variable is set to `FALSE`, a loose deduplication mechanism is used, which processes such queries as valid SQL queries. Added session variables `transactionreadonly` and `txreadonly` to specify the transaction access mode, which are compatible with MySQL versions 5.7.20 and above. Added the FE configuration item `routineloadunstablethresholdsecond`. Added the FE configuration item `httpworkerthreads_num`, which specifies the number of threads for HTTP server to deal with HTTP requests. The default value is `0`. If the value for this parameter is set to a negative value or 0, the actual thread number is twice the number of CPU cores. Added the BE configuration item `pindexmajorcompactionlimitper_disk` to configure the maximum concurrency of compaction on a disk. This addresses the issue of uneven I/O across disks due to compaction. This issue can cause excessively high I/O for certain disks. The default value is `1`. Fixed the following issues: Using NaN (Not a Number) columns as ORDER BY columns may cause BEs to crash. Failure to update primary key indexes may cause the error "getappliedrowsets failed". Hive metadata in is not automatically refreshed when new fields are added to Hive tables. When `SELECT ... FROM ... INTO OUTFILE` is executed to export data into CSV files, the error "Unmatched number of columns" is reported if the FROM clause contains multiple constants. In some cases, `bitmaptostring` may return incorrect result due to data type overflow. Release date: December 19, 2023 Added a new metric `maxtabletrowset_num` for setting the maximum allowed number of rowsets. This metric helps detect possible compaction issues and thus reduces the occurrences of the error "too many versions". Added the function. The result returned by the statement provides a new field `OtherMsg`, which shows information about the last failed task. The default retention period of trash files is changed to 1 day from the original 3 days. Optimized the performance of persistent index update when compaction is performed on all rowsets of a Primary Key table, which reduces disk read I/O. Optimized the logic used to compute compaction scores for Primary Key tables, thereby aligning the compaction scores for Primary Key tables within a more consistent range with the other three table types. Queries on MySQL external tables and the external tables within JDBC catalogs support including keywords in the WHERE clause. Added the bitmapfrombinary function to Spark Load to support loading Binary

The bRPC expiration time is shortened from 1 hour to the duration specified by the session variable . This prevents query failures caused by RPC request expiration. Added a BE configuration item `enablestreamloadverboselog` is added. The default value is `false`. With this parameter set to `true`, StarRocks can record the HTTP requests and responses for Stream Load jobs, making troubleshooting easier. Added a BE static parameter `updatecompactionpertabletminintervalseconds` becomes mutable. Fixed the following issues: Queries fail during hash joins, causing BEs to crash. The FE performance plunges after the FE configuration item `enablecollectquerydetailinfo` is set to `true`. Errors may be thrown if large amounts of data are loaded into a Primary Key table with persistent index enabled. The starrocks_be process may exit unexpectedly when `./agentctl.sh stop be` is used to stop a BE. The function occasionally causes the BEs to crash. Deadlocks may occur when users refresh materialized views. In some scenarios, dynamic partitioning may encounter an error, which causes FE start failures. Release date: December 1, 2023 Fixed the following issues: Global Runtime Filter may cause BEs to crash in certain scenarios. Release date: November 29, 2023 Added slow request logs to track slow requests. Optimized the performance of using Spark Load to read Parquet and ORC files when there are a large number of files. Optimized the performance of some Bitmap-related operations, including: Optimized nested loop joins. Optimized the `bitmap_xor` function. Supports Copy on Write to optimize Bitmap performance and reduce memory consumption. The FE dynamic parameter `enablenewpublish_mechanism` is changed to a static parameter. You must restart the FE after you modify the parameter settings. If a filtering condition is specified in a Broker Load job, BEs may crash during the data loading in certain circumstances. Failures in replaying replica operations may cause FEs to crash. Setting the FE parameter `recoverwithempty_tablet` to `true` may cause FEs to crash. The error "getappliedrowsets failed, tablet updates is in error state: tablet:18849 actual row size changed after compaction" is returned for queries. A query that contains a window function may cause BEs to crash. Running `show proc '/statistic'` may cause a deadlock. Errors may be thrown if large amounts of data are loaded into a Primary Key table with persistent index enabled. After StarRocks is upgraded from v2.4 or earlier to a later version, compaction scores may rise unexpectedly. If `INFORMATIONSCHEMA` is queried by using the database driver MariaDB ODBC, the `CATALOGNAME` column returned in the `schemata` view holds only `null` values. If schema changes are being executed while a Stream Load job is in the PREPARED state, a portion of the source data to be loaded by the job is lost. Including two or more slashes (`/`) at the end of the HDFS storage path causes the backup and restore of the data from HDFS to fail. Running a loading task or a query may cause the FEs to hang. Release date: November 14, 2023 The `COLUMNS` table in the system database `INFORMATION_SCHEMA` can display ARRAY, MAP, and STRUCT columns. Added a session variable `cbodecimalcaststringstrict`, which controls how the CBO converts data from the DECIMAL type to the STRING type. If this variable is set to `true`, the logic built in v2.5.x and later versions prevails and the system implements strict conversion (namely, the system truncates the generated string and fills 0s based on the scale length). If this variable is set to `false`, the logic built in versions earlier than v2.5.x prevails and the system processes all valid digits to generate a string. The default value is

Added a session variable `cboeqbase_type`, which specifies the data type used for data comparison between DECIMAL-type data and STRING-type data. The default value is `VARCHAR`, and DECIMAL is also a valid value. Fixed the following issues: The error `java.lang.IllegalStateException: null` is reported if the ON condition is nested with a subquery. The result of COUNT() is inconsistent among replicas if COUNT() is run immediately after `INSERT INTO SELECT ... LIMIT` is successfully executed. BE may crash for specific data types if the target data type specified in the cast() function is the same as the original data type. An error is reported if specific path formats are used during data loading via Broker Load: `msg:Fail to parse columnsFromPath, expected: During an upgrade to 3.x, if some column types are also upgraded (for example, Decimal is upgraded to Decimal v3), BEs crash when Compaction is performed on tables with specific characteristics. When data is loaded by using Flink Connector, the load job is suspended unexpectedly if there are highly concurrent load jobs and both the number of HTTP and Scan threads have reached their upper limits. BEs crash when libcurl is invoked. Adding BITMAP columns to a Primary Key table fails with the following error: `Analyze columnDef error: No aggregate function specified for 'userid'`. Long-time, frequent data loading into a Primary Key table with persistent index enabled may cause BEs to crash. The query result is incorrect when Query Cache is enabled. Specifying a nullable Sort Key when creating a Primary Key table causes compaction to fail. The error "StarRocks planner use long time 10000 ms in logical phase" occasionally occurs for complex Join queries. Release date: September 28, 2023 Window functions COVARSAMP, COVARPOP, CORR, VARIANCE, VARSAMP, STD, and STDDEVSAMP now support the ORDER BY clause and Window clause. An error instead of NULL is returned if a decimal overflow occurs during queries on the DECIMAL type data. Executing SQL commands with invalid comments now returns results consistent with MySQL. Rowsets corresponding to tablets that have been deleted are cleaned up, reducing the memory usage during BE startup. Fixed the following issues: An error "Set cancelled by MemoryScratchSinkOperator" occurs when users read data from StarRocks using the Spark Connector or Flink Connector. An error "java.lang.IllegalStateException: null" occurs during queries with an ORDER BY clause that includes aggregate functions. FEs fail to restart when there are inactive materialized views. Performing INSERT OVERWRITE operations on duplicate partitions corrupts the metadata, leading to FE restart failures. An error "java.lang.NullPointerException: null" occurs when users modify columns that do not exist in a Primary Key table. An error "get TableMeta failed from TNetworkAddress" occurs when users load data into a partitioned StarRocks external table. In certain scenarios, an error occurs when users load data via CloudCanal. An error "current running txns on db xxx is 200, larger than limit 200" occurs when users load data via the Flink Connector or perform DELETE and INSERT operations. Asynchronous materialized views which use HAVING clauses that include aggregate functions cannot rewrite queries properly. Release date: September 4, 2023 Comments in an SQL are retained in the Audit Log. Added CPU and memory statistics of INSERT INTO SELECT to the Audit Log. Fixed the following issues: When Broker Load is used to load data, the NOT NULL attribute of some fields may cause BEs to crash or cause the "msg:mismatched row count" error. Queries against ORC-formatted files fail because the bugfix ORC-1304 () from Apache ORC is not merged. Restoring Primary Key tables causes metadata inconsistency after BEs are

Release date: August 28, 2023 Supports implicit conversions for all compound predicates and for all expressions in the WHERE clause. You can enable or disable implicit conversions by using the `enablestricttype`. The default value is `false`. Optimized the prompt returned if users do not specify `hive.metastore.uri` when they create an Iceberg Catalog. The error prompt is more accurate. Added more prompts in the error message `xxx too many versions xxx`. Dynamic partitioning further supports the partitioning unit to be `year`. Fixed the following issues: When data is loaded into tables with multiple replicas, a large number of invalid log records are written if some partitions of the tables are empty. The DELETE operation fails if the field in the WHERE condition is a BITMAP or HLL field. Manually refreshing an asynchronous materialized view via a synchronous call (SYNC MODE) results in multiple INSERT OVERWRITE records in the `informationschema.taskruns` table. If CLONE operations are triggered on tablets in an ERROR state, disk usage increases. When Join Reorder is enabled, the query result is incorrect if the column to query is a constant. During tablet migration between SSDs and HDDs, if the FE sends excessive migration tasks to BEs, BEs will encounter OOM issues. The security vulnerability in `/apachehdfsbroker/lib/log4j-1.2.17.jar`. During data queries through Hive Catalog, if a partitioning column and an OR operator are used in the WHERE clause, the query result is incorrect. The error "java.util.ConcurrentModificationException: null" occasionally occurs during data queries. FEs cannot be restarted if the base table of an asynchronous materialized view is dropped. For an asynchronous materialized view that is created across databases, the Leader FE occasionally encounters a deadlock when data is being written into base tables of this materialized view. Release date: August 7, 2023 Supports aggregate functions , , and . Supports the following : COVARSAMP, COVARPOP, CORR, VARIANCE, VARSAMP, STD, and STDDEVSAMP. Optimized the scheduling logic of TabletChecker to prevent the checker from repeatedly scheduling tablets that are not repaired. When Schema Change and Routine Load occur simultaneously, Routine Load jobs may fail if Schema Change completes first. The error message reported in this situation is optimized. Users are prohibited from defining NOT NULL columns when they create external tables (If NOT NULL columns are defined, errors will occur after an upgrade and the table must be created again). External catalogs are recommended starting from v2.3.0 to replace external tables. Added an error message when Broker Load retries encounter an error. This facilitates troubleshooting and debugging during data loading. Supports large-scale data writes when a load job involves both UPSERT and DELETE operations. Optimized query rewrite using materialized views. Fixed the following issues: When CAST is used to convert a string into an array, the result may be incorrect if the input includes constants. SHOW TABLET returns incorrect results if it contains ORDER BY and LIMIT. Outer join and Anti join rewrite errors for materialized views. Incorrect table-level scan statistics in FE cause inaccurate metrics for table queries and loading. `An exception occurred when using the current long link to access metastore. msg: Failed to get next notification based on last event id: 707602` is reported in FE logs if event listener is configured on the HMS to incrementally update Hive metadata. The query result is not stable if the sort key is modified for a partitioned table. Data loaded using Spark Load may be distributed to the wrong buckets if the bucketing column is a DATE, DATETIME, or DECIMAL column. The regex_replace function may cause BEs to crash in some

BE crashes if the input of the sub_bitmap function is not a BITMAP value. "Unknown error" is returned for a query when Join Reorder is enabled. Inaccurate estimation of average row size causes Primary Key partial updates to occupy excessively large memory. Some INSERT jobs return ` If users specify `"hadoop.security.authentication" = "simple"` in their Broker Load jobs created to load data from HDFS, the job fails. Modifying the refresh mode of materialized views causes inconsistent metadata between the leader FE and follower FE. Passwords are not hidden when SHOW CREATE CATALOG and SHOW RESOURCES are used to query specific information. FE memory leak caused by blocked LabelCleaner threads. Release date: July 19, 2023 Queries that contain a different type of join than the materialized view can be rewritten. StarRocks external tables whose destination cluster is the current StarRocks cluster cannot be created. If the queried fields are not included in the output columns of a materialized view but are included in the predicate of the materialized view, the query can still be rewritten. Added a new field `tableid` to the table `tablesconfig` in the database `Informationschema`. You can join `tablesconfig` with `betablets` on the column `tableid` to query the names of the database and table to which a tablet belongs. Fixed the following issues: Count Distinct result is incorrect for Duplicate Key tables. BEs may crash if the Join key is a large BINARY column. The INSERT operation hangs if the length of CHAR data in a STRUCT to be inserted exceeds the maximum CHAR length defined in the STRUCT column. The result of coalesce() is incorrect. The version number for a tablet is inconsistent between the BE and FE after data is restored. Partitions cannot be automatically created for recovered tables. Release date: June 30, 2023 Optimized the error message reported when partitions are added to a non-partitioned table. Optimized the for tables. Optimized the default comments in the CREATE TABLE statement. Optimized the manual refreshing of asynchronous materialized views. Supports using the REFRESH MATERIALIZED VIEW WITH SYNC MODE syntax to synchronously invoke materialized view refresh tasks. Fixed the following issues: The COUNT result of an asynchronous materialized view may be inaccurate if the materialized view is built on Union results. "Unknown error" is reported when users attempt to forcibly reset the root password. Inaccurate error message is displayed when INSERT OVERWRITE is executed on a cluster with less than three alive BEs. Release date: June 14, 2023 Inactive materialized views can be manually activated using `ALTER MATERIALIZED VIEW <mv_name> ACTIVE`. You can use this SQL command to activate materialized views whose base tables were dropped and then recreated. For more information, see . StarRocks can automatically set an appropriate number of tablets when you create a table or add a partition, eliminating the need for manual operations. For more information, see . Optimized the I/O concurrency of Scan nodes used in external table queries, which reduces memory usage and improves the stability of data loading from external tables. Optimized the error message for Broker Load jobs. The error message contains retry information and the name of erroneous files. Optimized the error message returned when CREATE TABLE times out and added parameter tuning tips. Optimized the error message returned when ALTER TABLE fails because the table status is not Normal. Ignores full-width spaces in the CREATE TABLE statement. Optimized the Broker access timeout to increase the success rate of Broker Load jobs. For Primary Key tables, the `VersionCount` field returned by SHOW TABLET contains Rowsets that are in the Pending state. Optimized the Persistent Index

Fixed the following issues: When users load Parquet data into StarRocks, DATETIME values overflow during type conversion, causing data errors. Bucket information is lost after Dynamic Partitioning is disabled. Using unsupported properties in the CREATE TABLE statement causes null pointer exceptions (NPEs). Table permission filtering in `information_schema` becomes ineffective. As a result, users can view tables they do not have permission to. Information returned by SHOW TABLE STATUS is incomplete. A schema change sometimes may be hung if data loading occurs simultaneously with the schema change. RocksDB WAL flush blocks the brpc worker from processing bthreads, which interrupts high-frequency data loading into Primary Key tables. TIME-type columns that are not supported in StarRocks can be successfully created. Materialized view Union rewrite fails. Release date: May 19, 2023 Optimized the error message reported when INSERT INTO ... SELECT expires due to a small `thriftservermaxworkerthread` value. Tables created using CTAS have three replicas by default, which is consistent with the default replica number for common tables. Truncating partitions fails because the TRUNCATE operation is case-sensitive to partition names. Decommissioning BE fails due to the failure in creating temporary partitions for materialized views. Dynamic FE parameters that require an ARRAY value cannot be set to an empty array. Materialized views with the `partitionrefreshnumber` property specified may fail to completely refresh. SHOW CREATE TABLE masks cloud credential information, which causes incorrect credential information in memory. Predicates cannot take effect on some ORC files that are queried via external tables. The min-max filter cannot properly handle lower- and upper-case letters in column names. Late materialization causes errors in querying complex data types (STRUCT or MAP). The issue that occurs when restoring a Primary Key table. Release date: April 28, 2023 Added a metric to monitor the tablet status of Primary Key tables: Added the FE metric `errstatemetric`. Added the `ErrorStateTabletNum` column to the output of `SHOW PROC '/statistic/'` to display the number of err_state tablets. Added the `ErrorStateTablets` column to the output of `SHOW PROC '/statistic/<dbid>/'` to display the IDs of **errstate tablets. For more information, see . Optimized the disk balancing speed when multiple BEs are added. Optimized the inference of `storagemedium`. When BEs use both SSD and HDD as storage devices, if the property `storagecooldowntime` is specified, StarRocks sets `storagemedium` to `SSD`. Otherwise, StarRocks sets `storage_medium` to `HDD`. Optimized the performance of Unique Key tables by forbidding the collection of statistics from value columns. For Colocation tables, the replica status can be manually specified as `bad` by using statements like `ADMIN SET REPLICA STATUS PROPERTIES ("tabletid" = "10003", "backendid" = "10001", "status" = "bad");`. If the number of BEs is less than or equal to the number of replicas, the corrupted replica cannot be repaired. After a BE is started, its process exists but the BE port cannot be enabled. Wrong results are returned for aggregate queries whose subquery is nested with a window function. `autorefreshpartitions_limit` does not take effect when the materialized view (MV) is refreshed for the first time. As a result, all the partitions are refreshed. An error occurs when querying a CSV Hive external table whose array data is nested with complex data such as MAP and STRUCT. Queries that use Spark connector time out. If one replica of a two-replica table is corrupted, the table cannot recover. Query failure caused by MV query rewrite failure. The metric interface expires due to database lock. Wrong results are returned for Broadcast Join. NPE is returned when an unsupported data type is used in CREATE

The issue caused by using window_funnel() with the Query Cache feature. Optimization plan selection takes an unexpectedly long time after the CTE is rewritten. Release date: April 4, 2023 Optimized the performance of rewriting queries on materialized views during query planning. The amount of time taken for query planning is reduced by about 70%. Optimized the type inference logic. If a query like `SELECT sum(CASE WHEN XXX);` contains a constant `0`, such as `SELECT sum(CASE WHEN k1 = 1 THEN v1 ELSE 0 END) FROM test;`, pre-aggregation is automatically enabled to accelerate the query. Supports using `SHOW CREATE VIEW` to view the creation statement of a materialized view. Supports transmitting packets that are 2 GB or larger in size for a single bRPC request between BE nodes. Supports using to query the creation statement of an external catalog. The following bugs are fixed: After queries on materialized views are rewritten, the global dictionary for low-cardinality optimization does not take effect. If a query on materialized views fails to be rewritten, the query fails. If a materialized view is created based on a Primary Key or Unique Key table, queries on that materialized view cannot be rewritten. The column names of materialized views are case-sensitive. However, when you create a table, the table is successfully created without an error message even if column names are incorrect in the `PROPERTIES` of the table creation statement, and moreover the rewriting of queries on materialized views created on that table fails. After a query on materialized views is rewritten, the query plan ma contain partition column-based, invalid predicates, which affect query performance. When data is loaded into a newly created partition, queries on materialized views may fail to be rewritten. Configuring `"storage_medium" = "SSD"` at the creation of materialized views causes the refresh of the materialized views to fail. Concurrent compaction may happen on Primary Key tables. Compaction does not occur promptly after a large number of DELETE operations. If the expression of a statement contains multiple low-cardinality columns, the expression may fail to be properly rewritten. As a result, the global dictionary for low-cardinality optimization does not take effect. Release date: March 10, 2023 Optimized query rewrite for materialized views (MVs). Supports rewriting queries with Outer Join and Cross Join. Optimized the data scan logic for MVs, further accelerating the rewritten queries. Enhanced rewrite capabilities for single-table aggregate queries. Enhanced rewrite capabilities in View Delta scenarios, which is when the queried tables are a subset of the MV's base tables. Optimized the performance and memory usage when the window function RANK() is used as a filter or a sort key. The following bugs are fixed: Errors caused by null literals ` Misuse of the low-cardinality optimization dictionary in some complex query scenarios. The dictionary mapping check is now added before applying the dictionary. In a single BE environment, Local Shuffle causes GROUP BY to produce duplicate results. Misuses of partition-related PROPERTIES for a non-partitioned MV may cause the MV refresh to fail. The partition PROPERTIES check is now performed when users create an MV. Errors in parsing Parquet Repetition columns. The obtained column's nullable information is incorrect. Solution: When CTAS is used to create a Primary Key table, only the primary key columns are non-nullable; non-primary key columns are nullable. Some issues caused by deleting data from Primary Key tables. Release date: February 21, 2023 Supports using the Instance Profile and Assumed Role-based credential methods to access AWS S3 and AWS Glue. Supports the following bit functions: bitshiftleft, bitshiftright, and

Optimized the memory release logic, which significantly reduces peak memory usage when a query contains a large number of aggregate queries. Reduced the memory usage of sorting. The memory consumption is halved when a query involves window functions or sorting. The following bugs are fixed: Apache Hive external tables that contain MAP and ARRAY data cannot be refreshed. Superset cannot identify column types of materialized views. BI connectivity fails because SET GLOBAL/SESSION TRANSACTION cannot be parsed. The bucket number of dynamic partitioned tables in a Colocate Group cannot be modified and an error message is returned. Potential issues caused by a failure in the Prepare stage. Changed the default value of `enableexperimentalmv` from `false` to `true`, which means asynchronous materialized view is enabled by default. Added CHARACTER to the reserved keyword list. Release date: February 5, 2023 Asynchronous materialized views created based on external catalogs support query rewrite. Allows users to specify a collection period for automatic CBO statistics collection, which prevents cluster performance jitter caused by automatic full collection. Added Thrift server queue. Requests that cannot be processed immediately during INSERT INTO SELECT can be pending in the Thrift server queue, preventing requests from being rejected. Deprecated the FE parameter `defaultstoragemedium`. If `storagemedium` is not explicitly specified when users create a table, the system automatically infers the storage medium of the table based on BE disk type. For more information, see description of `storagemedium` in . The following bugs are fixed: Null pointer exception (NPE) caused by SET PASSWORD. JSON data with empty keys cannot be parsed. Data of invalid types can be successfully converted into ARRAY data. Nested Loop Join cannot be interrupted when an exception occurs. Deprecated the FE parameter `defaultstoragemedium`. The storage medium of a table is automatically inferred by the system. Release date: January 22, 2023 Supports querying Merge On Read tables using and . Supports querying STRUCT and MAP data using , Hudi catalogs, and . Provides to improve access performance of hot data stored in external storage systems, such as HDFS. Supports creating , which allow direct queries on data from Delta Lake. Hive, Hudi, and Iceberg catalogs are compatible with AWS Glue. Supports creating , which allow direct queries on Parquet and ORC files from HDFS and object stores. Supports creating materialized views based on Hive, Hudi, Iceberg catalogs, and materialized views. For more information, see . Supports conditional updates for tables that use the Primary Key table. For more information, see . Supports , which stores intermediate computation results of queries, improving the QPS and reduces the average latency of highly-concurrent, simple queries. Supports specifying the priority of Broker Load jobs. For more information, see Supports specifying the number of replicas for data loading for StarRocks native tables. For more information, see . Supports . Supports isolating compute resources occupied by data loading, thereby limiting the resource consumption of data loading tasks. For more information, see . Supports specifying the following data compression algorithms for StarRocks native tables: LZ4, Zstd, Snappy, and Zlib. For more information, see . Supports . Supports and the following higher-order functions: , , and . Provides the QUALIFY clause that filters the results of . Supports using the result returned by the uuid() and uuid_numeric() functions as the default value of a column when you create a table. For more information, see . Supports the following functions: , , , , , , , and . Optimized the metadata access performance when you query external data using , , and . Supports querying ARRAY data using

Optimized the following aspects of materialized views: Asynchronous materialized views support automatic and transparent query rewrite based on the SPJG-type materialized views. For more information, see . Asynchronous materialized views support multiple async refresh mechanisms. For more information, see . The efficiency of refreshing materialized views is improved. Optimized the following aspects of data loading: Optimized loading performance in multi-replica scenarios by supporting the "single leader replication" mode. Data loading gains a one-fold performance lift. For more information about "single leader replication", see `replicated_storage` in . Broker Load and Spark Load no longer need to depend on brokers for data loading when only one HDFS cluster or one Kerberos user is configured. However, if you have multiple HDFS clusters or multiple Kerberos users, you still need to deploy a broker. For more information, see and . Optimized the performance of Broker Load when a large number of small ORC files are loaded. Reduced the memory usage when you load data into Primary Key tables. Optimized the `informationschema` database and the `tables` and `columns` tables within. Adds a new table `tableconfig`. For more information, see . Optimized data backup and restore: Supports backing up and restoring data from multiple tables in a database at a time. For more information, see . Supports backing up and restoring data from Primary Key tables. For more information, see Backup and restore. Optimized the following functions: Added an optional parameter for the function, which is used to determine whether the beginning or end of the time interval is returned. Added a new mode `INCREASE` for the function to avoid computing duplicate timestamps. Supports specifying multiple arguments in the function. lead() and lag() functions support querying HLL and BITMAP data. For more information, see . The following ARRAY functions support querying JSON data: , , , , and . Optimized the use of some functions. The `currentdate`, `currenttimestamp`, `currenttime`, `localtimestamp`, and `localtime` functions can be executed without using `()`, for example, you can directly run `select currentdate;`. Removed some redundant information from FE logs. The following bugs are fixed: The appendtrailingcharifabsent() function may return an incorrect result when the first argument is empty. After a table is restored using the RECOVER statement, the table does not exist. The result returned by the SHOW CREATE MATERIALIZED VIEW statement does not contain the database and catalog specified in the query statement when the materialized view was created. Schema change jobs in the `waiting_stable` state cannot be canceled. Running the `SHOW PROC '/statistic';` command on a Leader FE and non-Leader FE returns different results. The position of the ORDER BY clause is incorrect in the result returned by SHOW CREATE TABLE. When users use Hive Catalog to query Hive data, if the execution plan generated by FE does not contain partition IDs, BEs fail to query Hive partition data. . Changed the default value of the `AWSEC2METADATA_DISABLED` parameter to `False`, which means that the metadata of Amazon EC2 is obtained to access AWS resources. Renamed session variable `isreportsuccess` to `enable_profile`, which can be queried using the SHOW VARIABLES statement. Added four reserved keywords: `CURRENTDATE`, `CURRENTTIME`, `LOCALTIME`, and `LOCALTIMESTAMP`. The maximum length of table and database names can be up to 1023 characters. BE configuration items `enableeventbasedcompactionframework` and `enablesizetieredcompactionstrategy` are set to `true` by default, which significantly reduces compaction overheads when there are a large number of tablets or a single tablet has large data volume. You can upgrade your cluster to 2.5.0 from 2.0.x, 2.1.x, 2.2.x, 2.3.x, or 2.4.x. However, if you need to perform a rollback, we recommend that you roll back only to 2.4.x.