Shipped · Databases

What StarRocks/starrocks shipped

The public repository of Starrocks · github.com/StarRocks/starrocks

Written by FoxPlug from the repository's own releases; not affiliated with Starrocks. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/StarRocks/starrocks; Starrocks did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for starrocks, free

Week of November 2, 2026

What shipped

Why it matters

This week brings four releases across the 4.0 and 4.1 lines, so users tracking either line get fixes for credential exposure in logs and endpoints, primary key insert behavior, and sample behavior on lake tables. Alongside the releases, the merged fixes target correctness issues users have hit in practice: overlapping Iceberg DATETIME partitions, colliding external materialized view partition names, unpadded CHAR from point lookups, and spurious decimal overflow errors on NULL rows. Operators doing shared-data migrations also get a narrower way to control lake compaction without disabling it globally.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Releases this week: 4.1.7, 4.1.6, 4.0.17, 4.0.16. Credential values masked in config endpoints and logs. Primary key inserts skip L1/L2 duplicate checks by default in local mode. Fixes for Iceberg DATETIME partitions, CHAR point lookups, and NULL-row decimal overflow.

Post for LinkedIn

This week StarRocks shipped 4.1.7, 4.1.6, 4.0.17 and 4.0.16. The 4.0.17 release masks credential values in BE and FE config endpoints and logs. In 4.1.7, local primary key inserts no longer check immutable L1 and L2 persistent-index files for duplicate keys by default, controlled by the skip_pindex_l1_l2_check_in_insert setting. Fixes landed for Iceberg identity partitions on DATETIME columns giving a one-second instead of one-day range, external materialized view partitions that stripped to the same name replacing each other, CHAR values returned padded from primary-key point lookups, and decimal overflow errors raised from NULL rows under ERROR_IF_OVERFLOW. Lake compaction also gains an opt-in table allowlist mode.

Week of October 26, 2026

What shipped

Why it matters

This week brings several correctness fixes for primary key inserts, materialized view pruning and string IN predicates in runtime filters, which frequent users of those features will notice. Unsupported geography operations are now rejected earlier during analysis, and geo descriptor handling in aggregates is more consistent. Documentation and test fixes also reduce flaky behavior in development.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: primary key column-subset INSERT can skip the partial update path on unwritten partitions, HAVING is normalized after constant key folding, string IN predicates avoid dictionary misreads, and unsupported geo operations are rejected in analysis.

Post for LinkedIn

This week's changes include a planner improvement so column-subset INSERT into primary key tables uses a plain insert when target partitions were never written, avoiding the partial update path. HAVING clauses are normalized after a constant group-by key is folded in, string IN predicates longer than the pushdown limit are no longer read as dictionary codes during runtime filter normalization, and materialized view pruning now preserves columns needed by late predicates. Unsupported scalar GEOGRAPHY and GEOMETRY operations are rejected during analysis, and geo descriptor handling in aggregate states is more consistent.

Week of October 19, 2026

What shipped

Why it matters

This week brings security integration authentication to HTTP, Arrow Flight SQL and the load RPCs, so directory-backed users are no longer limited to the MySQL protocol. Several correctness fixes land in JSON flattening, global dictionary handling across FEs, and aggregate spill paths, reducing decode failures and debug aborts. A privilege check on SHOW DATABASES FROM closes a gap where users without catalog access could still list its databases.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

StarRocks 4.0.17 is out. Security integration users can now authenticate over HTTP, Arrow Flight SQL and load RPCs. Also fixed: repeated-key JSON flattening, global dictionary renewal across FEs, SHOW DATABASES FROM privilege check, and aggregate spill issues.

Post for LinkedIn

StarRocks 4.0.17 is released. Security integration users can now authenticate over HTTP, Arrow Flight SQL and the load RPCs, not only through the MySQL protocol. This week also brings fixes for stored JSON that repeats a key, where flattening now emits one value per row; global dictionary renewal across FEs that caused Dict Decode failures on followers; an unsafe pointer in the JSON column compactor; and missing slice locks when reading min/max runtime filter bounds. SHOW DATABASES FROM an external catalog now checks catalog-level privilege first. Additional fixes cover bool_or merging an intermediate column with NULLs and a leak when an agg-state combinator batch-destroys.

Week of October 12, 2026

What shipped

Why it matters

This week is mostly about removing failure modes users hit in production: clearer errors when partitions vanish mid-load, no more EXPORT jobs cancelled seconds after starting, no BE crashes from oversized array_generate ranges, and MySQL-compatible truncation for CAST to CHAR(N). Several fixes also stop wrong answers, such as MIN and MAX read from LIST partition definitions and JSON subfield reads returning NULL. Alongside that, the storage and diagnostics tooling got narrower: segment dumps and tablet metadata dumps can be scoped, and rowsets migrated in shared-data now carry their vector index files.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Weekly StarRocks: CAST(x AS CHAR(N)) truncates like MySQL, INSERT OVERWRITE gives a clear error when a source partition disappears, EXPORT jobs stop being cancelled seconds after start, MIN/MAX on LIST partition columns no longer returns values no row holds, and local paths in th

Post for LinkedIn

This week in StarRocks: CAST(x AS CHAR(N)) now truncates to N characters like MySQL, INSERT OVERWRITE reports a clear error when a source partition is dropped or renamed before commit, and EXPORT jobs are no longer cancelled a few seconds after they start. MIN and MAX on single-column LIST partition columns no longer return values the data may not hold, mixed dictionary and non-dictionary aggregates are no longer rejected, an oversized array_generate range returns an error instead of taking down the BE, and credentials in SUBMIT TASK SQL are masked in task_run_history. Shared-data fixes cover primary key recover on V2-encoded single-column fixed-length keys, vector index files during rowset migration, and bundle metadata re-reads, and the diagnostics tools can now scope segment and tablet

Week of October 5, 2026

What shipped

Why it matters

This week is mostly correctness work on shared-data loads and external tables: aborted loads no longer leak index sstables, Paimon branch state and external statistics stay per-table, and writer filesystems survive cache eviction. Several fixes also make failures visible rather than silent, such as multi-table transaction commits that previously reported OK. Backport series keep connector I/O off FE metadata locks on the 4.0 and 4.1 branches.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: aborted shared-data loads now reclaim their PK index sstables, FULL OUTER JOIN USING keeps the join key type, CSV unload via INSERT INTO FILES accepts duplicate column names, and Paimon branch state is isolated per table.

Post for LinkedIn

This week's changes focus on shared-data loads and external tables. Aborted loads now reclaim their primary key index sstables instead of leaving them on object storage for full vacuum to miss. Paimon branch state is isolated per table so multi-table queries cannot apply one table's branch to another. CSV unload through INSERT INTO FILES now accepts duplicate output column names, a FULL OUTER JOIN USING column keeps its own type on the join key, and failed multi-table transaction commits report the failure rather than an OK status. External table statistics that failed to load are no longer cached as no statistics, and cache eviction no longer disconnects a filesystem still in use by a writer. Connector I/O stays off FE metadata locks on the 4.0 and 4.1 branches.

Week of September 28, 2026

What shipped

Why it matters

Two new releases ship improvements across spatial analytics with H3 indexing and coordinate transforms, geometry operations, and fixes for authorization, grouping, and security issues. The week covers native GEOMETRY enhancements and bug fixes that improve query correctness and operational security.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

StarRocks 4.1.6 and 4.0.16 released. New native H3 spatial indexing, SRID support, ST_Buffer and ST_Intersection operations. Fixes for Ranger authorization, GROUP BY correctness, and credential masking.

Post for LinkedIn

StarRocks 4.1.6 and 4.0.16 are now available. This week's releases include native H3 spatial indexing functions, SRID metadata and coordinate transforms for GEOMETRY, new polygon operations (ST_Buffer, ST_Intersection, ST_SimplifyPreserveTopology), and important fixes for Ranger authorization queries, GROUP BY ROLLUP/CUBE correctness, and object storage credential security.

Week of September 21, 2026

What shipped

Why it matters

This week fixes critical operational issues like memory reporting and metric inflation that affect cluster observability, adds spatial query support for geographic data, and improves LDAP/AD authentication handling. Several test infrastructure improvements ensure previously-hidden test cases now execute and catch regressions.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

StarRocks: GEO containment for spatial queries, ARM64 CPU detection, memory usage reporting fixed, LDAP case-insensitive auth, and metrics counting corrected.

Post for LinkedIn

StarRocks improvements this week: Native GEO containment predicates for POINT/POLYGON queries, ARM64 CPU feature detection (NEON, CRC32, SVE), fixed sys.fe_memory_usage reporting, case-insensitive LDAP/AD authentication, corrected QueryCumulativeCpuTime and QuerySpillBytes metrics, and materialized view rewrite fixes.

Week of September 14, 2026

What shipped

Why it matters

This week addresses correctness issues in query results, security vulnerabilities in dependencies, and lock contention problems in shared-data mode. The fixes span FULL OUTER JOIN correctness, prepared statement parameter binding, and metadata lock handling under connector I/O, which impact query reliability and cluster performance.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

StarRocks 4.1.3 ships with VARCHAR(N) length preservation in CTAS, native Iceberg GEOGRAPHY reads, and fixes for FULL OUTER JOIN value shifting, metadata lock contention, and security vulnerabilities.

Post for LinkedIn

StarRocks 4.1.3 is out with important correctness and performance fixes. FULL OUTER JOIN with multiple USING columns now returns accurate values, prepared statement caching respects parameter positions correctly, and metadata locks no longer block on external connector I/O. We've also added native Iceberg GEOGRAPHY support, made configuration more flexible with configurable publish timeouts, and patched security vulnerabilities in Apache Ranger and BouncyCastle.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-10.

Is this your repo? Ask us to remove this page.