Minor version | Release date | Description |
3.2.15-1.92 | March 21, 2025 | [New features] The window functions MAX_BY() and MIN_BY() are supported. [Optimized features] The time ranges during which base compaction operations are not allowed for tables can be specified. Statistics on Paimon tables can be collected. Metrics related to nodes and histograms are added. Timeout-related parameters can be configured for the StarRocks client. Automatic detection of replica files is supported. If the system detects that specific replica files are damaged, the system automatically marks them as bad files.
[Fixed issues] After the SHOW ROUTINE LOAD statement is executed, 0 is returned for the loadRowsRate field. The Files() function cannot correctly read columns that were not queried. FEs cannot respond because of the ARRAY_MAP function. FEs cannot respond because of metadata caching. Routine Load jobs are canceled due to transaction timeout. When low cardinality optimization is enabled, the execution plan for the nested aggregate function MAX(COUNT(DISTINCT)) is incorrect. Stream Load jobs are submitted to non-alive nodes. After BEs are restarted, the specific bRPC continuously reports errors. Stream Load jobs fail to be submitted by using HTTP 1.0. The job status of the leader and follower FEs is consistent. The number of rows in an MV is inaccurate.
|
3.2.11-1.79 | November 20, 2024 | [Optimized features] By default, partition-level caching is enabled for Paimon to accelerate queries. The statistics collection feature of Paimon is optimized. Error messages are returned when audit logs fail to be queried.
[Fixed issues] Colocate tablets are frequently migrated. The OSS scheme cannot be found during the access to Paimon tables stored in OSS or OSS-HDFS. Paimon tables cannot be created in DLF 2.0. A partition-related error occurs when data is written to Hive partitioned tables. An error occurs when the array_to_bitmap function is called to process constant arrays.
|
3.2.11-1.76 | October 30, 2024 | [Optimized features] The profile collection strategies are optimized, and specific crashes are fixed. The exception handling mechanism of the shared-data architecture is enhanced to improve system fault tolerance.
[Fixed issues] An error occurs when data is inserted into an external partitioned table. Abnormal FEs occurs due to thread leaks. The system crashes when primary key tables created in StarRocks shared-data instances contain fields of the bitmap type. Data in ToDataCacheInfo is leaked. This fix prevents an out-of-memory (OOM) error from occurring in the FEs of StarRocks shared-data instances. Incorrect query results are returned due to query caching. Incorrect results are returned by specific bucket shuffling operations. A null pointer exception occurs during the access to table functions.
|
3.2.9-1.71 | September 14, 2024 | [New features] [Optimized features] The EXPLAIN ANALYZE statement is supported for Paimon tables. The pruning and statistics collection features are no longer supported for Paimon tables. The SQL statements used by a query can be viewed. The performance of the SELECT COUNT statement is optimized. An interface is provided for obtaining migration progress. The dlf.catalog.id parameter can be configured when you create an Iceberg table.
[Fixed issues] |
3.2.9-1.67 | August 16, 2024 | [Optimized features] The performance of Hive Sink is improved. [Fixed issues] Hive catalogs are not adapted to Ranger. The system crashes due to the optimization of the COUNT statement. The refresh efficiency of MVs is low because the snapshot information takes a long period of time to obtain. Compaction Manager generates too much metadata for a table created in StarRocks shared-data instances. CNs are crashed due to specific reasons. After the minor version of a StarRocks instance is upgraded to 3.2.9, the PREPARE statements cannot work as expected. Data is inconsistency occurs after the spilling feature is enabled.
|
3.2.9-1.66 | August 09, 2024 | [New features] Data can be written to OSS-HDFS files even if the specific parent directory does not exist. Data stored in Jindo can be read by using the Broker Load mode. Different types of engines can be automatically identified by OSS-HDFS.
[Optimized features] Compaction logs are optimized for more efficient diagnostics and analysis. The star mgr directory is created when CNs are started. The default redirection configuration of FEs is optimized. Unnecessary logs and configuration items are optimized to improve performance. More I/O monitoring metrics are added for StarRocks shared-data instances to enhance the overall O&M capabilities. The adaptive I/O strategies are optimized for StarRocks shared-data instances.
[Fixed issues] External tables cannot be used to access data in Google Cloud Storage (GCS) and Microsoft Azure. The data size of the spilling result exceeds 4 GB. A pre-aggregation issue occurs during the spilling process. MVs are not refreshed as expected. An error occurs when memory statistics about primary keys are collected. The statistical information is inaccurate. Insert tasks cannot be canceled. An incorrect execution plan is generated due to schema changes. External tables cannot obtain information about CNs.
|
3.2.9-1.65 | July 19, 2024 | [New features] Jindo SDK is upgraded to 6.5.0. DLF catalogs are supported by Iceberg. Shard rebalancing is supported by StarRocks shared-data instances. The regexp_split function is supported.
[Optimized features] The default value of the get_txn_status_internal_sec parameter is reduced from 30 seconds to 10 seconds to prevent delays in the publish phase of Stream Load. The pindex_shared_data_gc_evict_interval_seconds parameter can be modified to change the garbage collection (GC) interval for the local persistent indexes of primary key tables created in StarRocks shared-data instances.
[Fixed issues] CRC mismatch occurs when data is exported to OSS by using Jindo. Files do not exist during the access to OSS-HDFS. The "Lost Connection" error message appears when specific SQL statements are executed.
|
3.2.8-1.62 | June 27, 2024 | [New features] Kudu and Paimon are supported by unified catalogs, and unified catalogs of the DLF type can be created. Generation of lineage logs is supported. The comments of external tables can be viewed by executing the DESCRIBE and SHOW CREATE statements.
[Fixed issues] Data cannot be written to the external tables of StarRocks shared-data instances. When the partition columns contain NULL values, the MVs of Paimon cannot be refreshed. The memory statistics is inaccurate.
|
3.2.6-1.60 | June 6, 2024 | [New features] [Optimized features] The enable_pipeline_engine parameter is added. [Fixed issues] BEs crash because a migration task fails to obtain the schema of the source. The memory statistics is inaccurate. An performance error occurs when Paimon reads data from read-only tables.
|
3.2.6-1.59 | May 31, 2024 | [New features] Information about bad SQL statements is displayed in the query details. [Optimized features] The delete vector can be used by Paimon to perform queries. [Fixed issues] |
3.2.6-1.57 | May 23, 2024 |
Note If you use a StarRocks instance whose minor version is earlier than 3.2.6-1.57, we recommend that you upgrade the instance to 3.2.6-1.57 or a later minor version. [New features] The OPTIMIZE command can be used to optimize the bucket storage layout of internal tables created in StarRocks shared-data instances. [Optimized features] The fragment_profile_drop_threshold_ms configuration item is added for the FEs and can be configured in the EMR console based on your business requirements. The default value of the drop fragment profile is set to 0 to disable the specific feature. The lake_flush_thread_num_per_store configuration item is added to allow you to refresh internal tables created in StarRocks shared-data instances. This improves the write I/O throughput. The default value is calculated by using the following formula: 2 × Number of CPUs . I/O merge strategies are optimized to merge small files. This allows you to directly read the merged file. The default values of the configuration items that are used for cross-instance migration are changed.
[Fixed issues] The connection to the RPC interface report_exec_stat fails and cannot be established after retries. This issue may cause failures of INSERT INTO operations and profile collection. After MV indexes are introduced, FEs frequently crash during metadata replay. After the abstract syntax tree (AST) cache mechanism is introduced from version 3.2.6, specific materialized views cannot be created.
|
3.2.6-1.52 | May 8, 2024 | [New features] DLF databases and tables can be created and managed in EMR Serverless StarRocks. [Fixed issues] After the lake_tablet_internal_parallel parameter is set to true, tablet metadata fails to be obtained and an error message is displayed. An import job in INSERT INTO mode times out. The thrift_rpc_timeout_ms configuration item is added for the BEs to adjust the RPC timeout. After an operation related to schema change is performed, no response is returned for a long period of time.
|
3.2.4-1.37 | March 08, 2024 | |