Skip to main content

StarRocks version 3.2


Release date: March 12, 2024

New Features

  • Cloud-native Primary Key tables in shared-data clusters support Size-tiered Compaction to reduce the write I/O amplification. #41034
  • Added the date function milliseconds_diff. #38171
  • Added the session variable catalog, which specifies the catalog to which the session belongs. #41329
  • Supports setting user-defined variables in hints. #40746
  • Supports CREATE TABLE LIKE in Hive catalogs. #37685
  • Added the view information_schema.partitions_meta, which records detailed metadata of partitions. #39265
  • Added the view sys.fe_memory_usage, which records the memory usage for StarRocks. #40464

Behavior Changes

  • cbo_decimal_cast_string_strict is used to control how CBO converts data from the DECIMAL type to the STRING type. The default value true indicates that 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). The DECIMAL type is not strictly filled in earlier versions, causing different results when comparing the DECIMAL type and the STRING type. #40619
  • The default value of the Iceberg Catalog parameter enable_iceberg_metadata_cache has been changed to false. From v3.2.1 to v3.2.3, this parameter is set to true by default, regardless of what metastore service is used. In v3.2.4 and later, if the Iceberg cluster uses AWS Glue as metastore, this parameter still defaults to true. However, if the Iceberg cluster uses other metastore service such as Hive metastore, this parameter defaults to false. #41826
  • The user who can refresh materialized views is changed from the root user to the user who creates the materialized views. This change does not affect existing materialized views. #40670
  • By default, when comparing columns of constant and string types, StarRocks compares them as strings. Users can use the session variable cbo_eq_base_type to adjust the rule used for the comparison. For example, users can set cbo_eq_base_type to decimal, and StarRocks then compares the columns as numeric values. #40619


  • Shared-data StarRocks clusters support the Partitioned Prefix feature for S3-compatible object storage systems. When this feature is enabled, StarRocks stores the data into multiple, uniformly prefixed partitions (sub-paths) under the bucket. This improves the read and write efficiency on data files in S3-compatible object storages. #41627
  • StarRocks supports using the parameter s3_compatible_fs_list to specify which S3-compatible object storage can be accessed via AWS SDK, and supports using the parameter fallback_to_hadoop_fs_list to specify non-S3-compatible object storages that require access via HDFS Schema (this method requires the use of vendor-provided JAR packages). #41123
  • Optimized compatibility with Trino. Supports syntax conversion from the following Trino functions: current_catalog, current_schema, to_char, from_hex, to_date, to_timestamp, and index. #41217 #41319 #40803
  • Optimized the query rewrite logic of materialized views. StarRocks can rewrite queries with materialized views created upon logical views. #42173
  • Improved the efficiency of converting the STRING type to the DATETIME type by 35% to 40%. #41464
  • The agg_type of BITMAP-type columns in an Aggregate table can be set to replace_if_not_null in order to support updates only to a few columns of the table. #42034
  • Improved the Broker Load performance when loading small ORC files. #41765
  • The tables with hybrid row-column storage support Schema Change. #40851
  • The tables with hybrid row-column storage support complex types including BITMAP, HLL, JSON, ARRAY, MAP, and STRUCT. #41476
  • A new internal SQL log file is added to record log data related to statistics and materialized views. #40453

Bug Fixes

Fixed the following issues:

  • "Analyze Error" is thrown if inconsistent letter cases are assigned to the names or aliases of tables or views queried in the creation of a Hive view. #40921
  • I/O usage reaches the upper limit if persistent indexes are created on Primary Key tables. #39959
  • In shared-data clusters, primary key index directories are deleted every 5 hours. #40745
  • After users execute ALTER TABLE COMPACT by hand, the memory usage statistics for compaction operations are abnormal. #41150
  • Retries of the Publish phase may hang for Primary Key tables. #39890


Release date: February 8, 2024

New Features

  • [Preview] Supports hybrid row-column storage for tables. It allows better performance for high-concurrency, low-latency point lookups against Primary Key tables and partial data updates. Currently, this feature does not support modification via ALTER TABLE, changing Sort Key, and partial updates in column mode.
  • Supports backing up and restoring asynchronous materialized views.
  • Broker Load supports loading JSON-type data.
  • Supports query rewrite using asynchronous materialized views created upon views. Queries against a view can be rewritten based on materialized views that are created upon that view.
  • Supports CREATE OR REPLACE PIPE. #37658

Behavior Changes

  • Added the session variable enable_strict_order_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. #37910
  • Added the session variable enable_materialized_view_for_insert, which controls whether materialized views rewrite the queries in INSERT INTO SELECT statements. The default value is false. #37505
  • When a single query is executed within the Pipeline framework, its memory limit is now constrained by the variable query_mem_limit instead of exec_mem_limit. Setting the value of query_mem_limit to 0 indicates no limit. #34120

Parameter Changes

  • Added the FE configuration item http_worker_threads_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. #37530
  • Added the BE configuration item lake_pk_compaction_max_input_rowsets, which controls the maximum number of input rowsets allowed in a Primary Key table compaction task in a shared-data StarRocks cluster. This helps optimize resource consumption for compaction tasks. #39611
  • Added the session variable connector_sink_compression_codec, which specifies the compression algorithm used for writing data into Hive tables or Iceberg tables, or exporting data with Files(). Valid algorithms include GZIP, BROTLI, ZSTD, and LZ4. #37912
  • Added the FE configuration item routine_load_unstable_threshold_second. #36222
  • Added the BE configuration item pindex_major_compaction_limit_per_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. #36681
  • Added the BE configuration item enable_lazy_delta_column_compaction. The default value is true, indicating that StarRocks does not perform frequent compaction operations on delta columns. #36654
  • Added the FE configuration item default_mv_refresh_immediate, which specifies whether to immediately refresh the materialized view after the materialized view is created. The default value is true. #37093
  • Changed the default value of the FE configuration item default_mv_refresh_partition_numto 1. This indicates that when multiple partitions need to be updated during a materialized view refresh, the task will be split in batches, refreshing only one partition at a time. This helps reduce resource consumption during each refresh. #36560
  • Changed the default value of the BE/CN configuration item starlet_use_star_cache to true. This indicates that block data cache is enabled by default in shared-data clusters. If, before upgrading, you have manually configured the BE/CN configuration item starlet_cache_evict_high_water to X, you must configure the BE/CN configuration item starlet_star_cache_disk_size_percent to (1.0 - X) * 100. For example, if you have set starlet_cache_evict_high_water to 0.3 before upgrading, you must set starlet_star_cache_disk_size_percent to 70. This ensures that both file data cache and block data cache will not exceed the disk capacity limit. #38200


  • Added date formats yyyy-MM-ddTHH:mm and yyyy-MM-dd HH:mm to support TIMESTAMP partition fields in Apache Iceberg tables. #39986
  • Added Data Cache-related metrics to the monitoring API. #40375
  • Optimized BE log printing to prevent too many irrelevant logs. #22820 #36187
  • Added the field storage_medium to the view information_schema.be_tablets. #37070
  • Supports SET_VAR in multiple sub-queries. #36871
  • A new field LatestSourcePosition is added to the return result of SHOW ROUTINE LOAD to record the position of the latest message in each partition of the Kafka topic, helping check the latencies of data loading. #38298
  • When the string on the right side of the LIKE operator within the WHERE clause does not include % or _, the LIKE operator is converted into the = operator. #37515
  • The default retention period of trash files is changed to 1 day from the original 3 days. #37113
  • Supports collecting statistics from Iceberg tables with Partition Transform. #39907
  • The scheduling policy for Routine Load is optimized, so that slow tasks do not block the execution of the other normal tasks. #37638

Bug Fixes

Fixed the following issues:

  • The execution of ANALYZE TABLE gets stuck occasionally. #36836
  • The memory consumption by PageCache exceeds the threshold specified by the BE dynamic parameter storage_page_cache_limit in certain circumstances. #37740
  • Hive metadata in Hive catalogs is not automatically refreshed when new fields are added to Hive tables. #37549
  • In some cases, bitmap_to_string may return incorrect results due to data type overflow. #37405
  • 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. #38045
  • In some cases, querying semi-structured data in tables may cause BEs to crash. #40208


Release date: December 30, 2023

Bug Fixes

Fixed the following issue:

  • When StarRocks is upgraded from v3.1.2 or earlier to v3.2, FEs may fail to restart. #38172


Release date: December 21, 2023

New Features

Data Lake Analytics

  • Supports reading Hive Catalog tables and file external tables in Avro, SequenceFile, and RCFile formats through Java Native Interface (JNI).

Materialized View

  • Added a view object_dependencies to the database sys. It contains the lineage information of asynchronous materialized views. #35060
  • Supports creating synchronous materialized views with the WHERE clause.
  • Supports partition-level incremental refresh for asynchronous materialized views created upon Iceberg catalogs.
  • [Preview] Supports creating asynchronous materialized views based on tables in a Paimon catalog with partition-level refresh.

Query and SQL functions

Monitoring and alerts

  • Added a new metric max_tablet_rowset_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". #36539

Parameter change

  • A new BE configuration item enable_stream_load_verbose_log 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. #36113


  • Upgraded the default GC algorithm in JDK8 to G1. #37268
  • A new value option GROUP_CONCAT_LEGACY is added to the session variable sql_mode to provide compatibility with the implementation logic of the group_concat function in versions earlier than v2.5. #36150
  • The authentication information aws.s3.access_key and aws.s3.access_secret for AWS S3 in Broker Load jobs are hidden in audit logs. #36571
  • The be_tablets view in the information_schema database provides a new field INDEX_DISK, which records the disk usage (measured in bytes) of persistent indexes. #35615
  • The result returned by the SHOW ROUTINE LOAD statement provides a new field OtherMsg, which shows information about the last failed task. #35806

Bug Fixes

Fixed the following issues:

  • The BEs crash if users create persistent indexes in the event of data corruption.#30841
  • The array_distinct function occasionally causes the BEs to crash. #36377
  • After the DISTINCT window operator pushdown feature is enabled, errors are reported if SELECT DISTINCT operations are performed on the complex expressions of the columns computed by window functions. #36357
  • Some S3-compatible object storage returns duplicate files, causing the BEs to crash. #36103


Release date: December 1, 2023

New Features

Shared-data cluster

  • Supports persisting indexes of Primary Key tables to local disks.
  • Supports even distribution of Data Cache among multiple local disks.

Materialized View

Asynchronous materialized view

  • The Query Dump file can include information of asynchronous materialized views.
  • The Spill to Disk feature is enabled by default for the refresh tasks of asynchronous materialized views, reducing memory consumption.

Data Lake Analytics

  • Supports creating and dropping databases and managed tables in Hive catalogs, and supports exporting data to Hive's managed tables using INSERT or INSERT OVERWRITE.
  • Supports Unified Catalog, with which users can access different table formats (Hive, Iceberg, Hudi, and Delta Lake) that share a common metastore like Hive metastore or AWS Glue.
  • Supports collecting statistics of Hive and Iceberg tables using ANALYZE TABLE, and storing the statistics in StarRocks, thus facilitating optimization of query plans and accelerating subsequent queries.
  • Supports Information Schema for external tables, providing additional convenience for interactions between external systems (such as BI tools) and StarRocks.

Storage engine, data ingestion, and export

  • Added the following features of loading with the table function FILES():
    • Loading Parquet and ORC format data from Azure or GCP.
    • Extracting the value of a key/value pair from the file path as the value of a column using the parameter columns_from_path.
    • Loading complex data types including ARRAY, JSON, MAP, and STRUCT.
  • Supports unloading data from StarRocks to Parquet-formatted files stored in AWS S3 or HDFS by using INSERT INTO FILES. For detailed instructions, see Unload data using INSERT INTO FILES.
  • Supports manual optimization of table structure and data distribution strategy used in an existing table to optimize the query and loading performance. You can set a new bucket key, bucket number, or sort key for a table. You can also set a different bucket number for specific partitions.
  • Supports continuous data loading from AWS S3 or HDFS using the PIPE method.
    • When PIPE detects new or modifications in a remote storage directory, it can automatically load the new or modified data into the destination table in StarRocks. While loading data, PIPE automatically splits a large loading task into smaller, serialized tasks, enhancing stability in large-scale data ingestion scenarios and reducing the cost of error retries.


  • Supports HTTP SQL API, enabling users to access StarRocks data via HTTP and execute SELECT, SHOW, EXPLAIN, or KILL operations.
  • Supports Runtime Profile and text-based Profile analysis commands (SHOW PROFILELIST, ANALYZE PROFILE, EXPLAIN ANALYZE) to allow users to directly analyze profiles via MySQL clients, facilitating bottleneck identification and discovery of optimization opportunities.

SQL reference

Added the following functions:

  • String functions: substring_index, url_extract_parameter, url_encode, url_decode, and translate
  • Date functions: dayofweek_iso, week_iso, quarters_add, quarters_sub, milliseconds_add, milliseconds_sub, date_diff, jodatime_format, str_to_jodatime, to_iso8601, to_tera_date, and to_tera_timestamp
  • Pattern matching function: regexp_extract_all
  • hash function: xx_hash3_64
  • Aggregate functions: approx_top_k
  • Window functions: cume_dist, percent_rank and session_number
  • Utility functions: get_query_profile and is_role_in_session

Privileges and security

StarRocks supports access control through Apache Ranger, providing a higher level of data security and allowing the reuse of existing services of external data sources. After integrating with Apache Ranger, StarRocks enables the following access control methods:

  • When accessing internal tables, external tables, or other objects in StarRocks, access control can be enforced based on the access policies configured for the StarRocks Service in Ranger.
  • When accessing an external catalog, access control can also leverage the corresponding Ranger service of the original data source (such as Hive Service) to control access (currently, access control for exporting data to Hive is not yet supported).

For more information, see Manage permissions with Apache Ranger.


Data Lake Analytics

  • Optimized ORC Reader:
    • Optimized the ORC Column Reader, resulting in nearly a two-fold performance improvement for VARCHAR and CHAR data reading.
    • Optimized the decompression performance of ORC files in Zlib compression format.
  • Optimized Parquet Reader:
    • Supports adaptive I/O merging, allowing adaptive merging of columns with and without predicates based on filtering effects, thus reducing I/O.
    • Optimized Dict Filter for faster predicate rewriting. Supports STRUCT sub-columns, and on-demand dictionary column decoding.
    • Optimized Dict Decode performance.
    • Optimized late materialization performance.
    • Supports caching file footers to avoid repeated computation overhead.
    • Supports decompression of Parquet files in lzo compression format.
  • Optimized CSV Reader:
    • Optimized the Reader performance.
    • Supports decompression of CSV files in Snappy and lzo compression formats.
  • Optimized the performance of the count calculation.
  • Optimized Iceberg Catalog capabilities:
    • Supports collecting column statistics from Manifest files to accelerate queries.
    • Supports collecting NDV (number of distinct values) from Puffin files to accelerate queries.
    • Supports partition pruning.
    • Reduced Iceberg metadata memory consumption to enhance stability in scenarios with large metadata volume or high query concurrency.

Materialized View

Asynchronous materialized view

  • Supports automatic refresh for an asynchronous materialized view created upon views or materialized views when schema changes occur on the views, materialized views, or their base tables.
  • Data consistency:
    • Added the property query_rewrite_consistency for asynchronous materialized view creation. This property defines the query rewrite rules based on the consistency check.
    • Add the property force_external_table_query_rewrite for external catalog-based asynchronous materialized view creation. This property defines whether to allow force query rewrite for asynchronous materialized views created upon external catalogs.
    • For detailed information, see CREATE MATERIALIZED VIEW.
  • Added a consistency check for materialized views' partitioning key.
    • When users create an asynchronous materialized view with window functions that include a PARTITION BY expression, the partitioning column of the window function must match that of the materialized view.

Storage engine, data ingestion, and export

  • Optimized the persistent index for Primary Key tables by improving memory usage logic while reducing I/O read and write amplification. #24875 #27577 #28769
  • Supports data re-distribution across local disks for Primary Key tables.
  • Partitioned tables support automatic cooldown based on the partition time range and cooldown time. Compared to the original cooldown logic, it is more convenient to perform hot and cold data management on the partition level. For more information, see Specify initial storage medium, automatic storage cooldown time, replica number.
  • The Publish phase of a load job that writes data into a Primary Key table is changed from asynchronous mode to synchronous mode. As such, the data loaded can be queried immediately after the load job finishes. For more information, see enable_sync_publish.
  • Supports Fast Schema Evolution, which is controlled by the table property fast_schema_evolution. After this feature is enabled, the execution efficiency of adding or dropping columns is significantly improved. This mode is disabled by default (Default value is false). You cannot modify this property for existing tables using ALTER TABLE.
  • Supports dynamically adjusting the number of tablets to create according to cluster information and the size of the data for Duplicate Key tables created with the Radom Bucketing strategy.


  • Optimized StarRocks' compatibility with Metabase and Superset. Supports integrating them with external catalogs.

SQL Reference

  • array_agg supports the keyword DISTINCT.
  • INSERT, UPDATE, and DELETE operations now support SET_VAR. #35283


  • Added the session variable large_decimal_underlying_type = "panic"|"double"|"decimal" to set the rules to deal with DECIMAL type overflow. panic indicates returning an error immediately, double indicates converting the data to DOUBLE type, and decimal indicates converting the data to DECIMAL(38,s).

Developer tools

  • Supports Trace Query Profile for asynchronous materialized views, which can be used to analyze its transparent rewrite.

Behavior Change

To be updated.

Parameter Change

FE Parameters

  • Added the following FE configuration items:
    • catalog_metadata_cache_size
    • enable_backup_materialized_view
    • enable_colocate_mv_index
    • enable_fast_schema_evolution
    • json_file_size_limit
    • lake_enable_ingest_slowdown
    • lake_ingest_slowdown_threshold
    • lake_ingest_slowdown_ratio
    • lake_compaction_score_upper_bound
    • mv_auto_analyze_async
    • primary_key_disk_schedule_time
    • statistic_auto_collect_small_table_rows
    • stream_load_task_keep_max_num
    • stream_load_task_keep_max_second
  • Removed FE configuration item enable_pipeline_load.
  • Default value modifications:
    • The default value of enable_sync_publish is changed from false to true.
    • The default value of enable_persistent_index_by_default is changed from false to true.

BE Parameters

  • Data Cache-related configuration changes.

    • Added datacache_enable to replace block_cache_enable.
    • Added datacache_mem_size to replace block_cache_mem_size.
    • Added datacache_disk_size to replace block_cache_disk_size.
    • Added datacache_disk_path to replace block_cache_disk_path.
    • Added datacache_meta_path to replace block_cache_meta_path.
    • Added datacache_block_size to replace block_cache_block_size.
    • Added datacache_checksum_enable to replace block_cache_checksum_enable.
    • Added datacache_direct_io_enable to replace block_cache_direct_io_enable.
    • Added datacache_max_concurrent_inserts to replace block_cache_max_concurrent_inserts.
    • Added datacache_max_flying_memory_mb.
    • Added datacache_engine to replace block_cache_engine.
    • Removed block_cache_max_parcel_memory_mb.
    • Removed block_cache_report_stats.
    • Removed block_cache_lru_insertion_point.

    After renaming Block Cache to Data Cache, StarRocks has introduced a new set of BE parameters prefixed with datacache to replace the original parameters prefixed with block_cache. After upgrade to v3.2, the original parameters will still be effective. Once enabled, the new parameters will override the original ones. The mixed usage of new and original parameters is not supported, as it may result in some configurations not taking effect. In the future, StarRocks plans to deprecate the original parameters with the block_cache prefix, so we recommend you use the new parameters with the datacache prefix.

  • Added the following BE configuration items:

    • spill_max_dir_bytes_ratio
    • streaming_agg_limited_memory_size
    • streaming_agg_chunk_buffer_size
  • Removed the following BE configuration items:

    • Dynamic parameter tc_use_memory_min
    • Dynamic parameter tc_free_memory_rate
    • Dynamic parameter tc_gc_period
    • Static parameter tc_max_total_thread_cache_byte
  • Default value modifications:

    • The default value of disable_column_pool is changed from false to true.
    • The default value of thrift_port is changed from 9060 to 0.
    • The default value of enable_load_colocate_mv is changed from false to true.
    • The default value of enable_pindex_minor_compaction is changed from false to true.

System Variables

  • Added the following session variables:
    • enable_per_bucket_optimize
    • enable_write_hive_external_table
    • hive_temp_staging_dir
    • spill_revocable_max_bytes
    • thrift_plan_protocol
  • Removed the following session variables:
    • enable_pipeline_query_statistic
    • enable_deliver_batch_fragments
  • Renamed the following session variables:
    • enable_scan_block_cache is renamed as enable_scan_datacache.
    • enable_populate_block_cache is renamed as enable_populate_datacache.

Reserved Keywords

Added reserved keywords OPTIMIZE and PREPARE.

Bug Fixes

Fixed the following issues:

  • BEs crash when libcurl is invoked. #31667
  • Schema Change may fail if it takes an excessively long period of time, because the specified tablet version is handled by garbage collection. #31376
  • Failed to access the Parquet files in MinIO via file external tables. #29873
  • The ARRAY, MAP, and STRUCT type columns are not correctly displayed in information_schema.columns. #33431
  • An error is reported if specific path formats are used during data loading via Broker Load: msg:Fail to parse columnsFromPath, expected: [rec_dt]. #32720
  • DATA_TYPE and COLUMN_TYPE for BINARY or VARBINARY data types are displayed as unknown in the information_schema.columns view. #32678
  • Complex queries that involve many unions, expressions, and SELECT columns can result in a sudden surge in the bandwidth or CPU usage within an FE node.
  • The refresh of asynchronous materialized view may occasionally encounter deadlock. #35736

Upgrade Notes

  • Optimization on Random Bucketing is disabled by default. To enable it, you need to add the property bucket_size when creating tables. This allows the system to dynamically adjust the number of tablets based on cluster information and the size of loaded data. Please note that once this optimization is enabled, if you need to roll back your cluster to v3.1 or earlier, you must delete tables with this optimization enabled and manually execute a metadata checkpoint (by executing ALTER SYSTEM CREATE IMAGE). Otherwise, the rollback will fail.
  • Starting from v3.2.0, StarRocks has disabled non-Pipeline queries. Therefore, before upgrading your cluster to v3.2, you need to globally enable the Pipeline engine (by adding the configuration enable_pipeline_engine=true in the FE configuration file fe.conf). Failure to do so will result in errors for non-Pipeline queries.