Shipped · Databases

What risingwavelabs/risingwave shipped

The public repository of Risingwave · github.com/risingwavelabs/risingwave

Written by FoxPlug from the repository's own releases; not affiliated with Risingwave. 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/risingwavelabs/risingwave; Risingwave 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 risingwave, free

Week of November 2, 2026

What shipped

Why it matters

This week brought a new release plus a new CDC source and fixes targeting query correctness, sink reliability and connectivity. Users of BigQuery, ClickHouse, Kafka, Kinesis, SQL Server and Postgres CDC get fixes, and several storage and compaction issues were addressed in the background.

Changelog entry

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

Post for X

RisingWave v3.1.1 is out. This week: a new MariaDB CDC source, fixed scan range pushdown results, and no more empty BigQuery AppendRows requests. BigQuery upserts are now ordered by change sequence number, and SQL Server and Postgres CDC handle dotted table names.

Post for LinkedIn

RisingWave v3.1.1 is released. This week also added a first-class MariaDB CDC source and fixed wrong results and a possible panic in scan range pushdown. The BigQuery sink no longer sends empty AppendRows requests, and BigQuery upsert changes are ordered with a change sequence number, both backported to earlier release branches. SQL Server and Postgres CDC now support table names containing a dot, DROP CONNECTOR works on refreshable tables, and stored definitions that fail to parse return an error instead of being accepted.

Week of October 26, 2026

What shipped

Why it matters

This week fixed several query correctness issues that could give wrong rows, including full outer join output, array subqueries and watermark derivation. It also tightened parser behavior and table DDL checks. CDC and connector handling got fixes for offset commits, Kinesis retry parsing and Debezium topic naming.

Changelog entry

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

Post for X

Weekly roundup: generated columns now enforce NOT NULL, IS NOT DISTINCT FROM parses tighter than AND/OR, escaped quoted identifiers work, and several query correctness fixes landed for outer joins, array subqueries and watermarks.

Post for LinkedIn

This week's changes to the repository focus on query correctness and connector behavior. Generated columns now enforce NOT NULL, and IS [NOT] DISTINCT FROM is parsed tighter than AND and OR. Escaped double-quoted identifiers are tokenized correctly, full outer hash joins with non-equi conditions no longer add NULL rows, correlated ARRAY subqueries no longer emit transient NULLs in materialized views, and watermarks are no longer derived through timestamp plus or minus months. On the CDC side, offsets persisted on non-checkpoint barriers are committed, Kinesis reader retry intervals parse from strings, and Debezium topic names keep table names unsanitized.

Week of October 19, 2026

What shipped

Why it matters

This week brings new Iceberg capabilities, including orphan file cleanup, coordinated PK-index compaction, and V3 change log truncation, plus improved catalog authentication for Google-backed storage. Connector support widens with native Pulsar JSON schemas, and a set of correctness fixes addresses query scoping, BigQuery upsert ordering, and CDC behavior. Users of CDC sources and Iceberg sinks get fewer failure paths and more predictable results.

Changelog entry

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

Post for X

This week: Iceberg orphan file cleanup, coordinated PK-index compaction, Iceberg V3 change log truncation, GCS vended credentials with Google auth, native Pulsar JSON schemas, and database filters in diagnostic reports. Several fixes for correlated subqueries, BigQuery upsert ord

Post for LinkedIn

This week the project added Iceberg orphan file cleanup, meta coordination of PK-index Iceberg compaction, Iceberg V3 change log truncation, and GCS vended credentials with native Google authentication for Iceberg REST catalogs. Connector support widened with native Pulsar JSON schemas, and diagnostic reports can now be filtered by database. A range of fixes landed as well: correlated references bind to their owning scope, BigQuery upsert changes are ordered by _CHANGE_SEQUENCE_NUMBER, state table reads hide rows below the pending watermark, and base64 Pub/Sub credentials work again. CDC sources also received fixes for privilege checks, SQL Server name casing and binlog monitoring.

Week of October 12, 2026

What shipped

Why it matters

This week brings fixes across streaming correctness, CDC recovery and Iceberg handling, plus a new SQL Server query function and automatic Oracle heartbeat table setup. Users of as of joins, TTL tables, over-window aggregations and Pulsar or SQL Server sources get behavior fixes, and storage compaction gains bounded index planning.

Changelog entry

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

Post for X

This week: asof joins clean both sides by watermark, Iceberg V3 compaction with barriers, new mssql_query table function, automatic Oracle heartbeat tables, and fixes for streaming sum, TTL expiry and CDC backfill recovery.

Post for LinkedIn

This week's RisingWave changes cover streaming correctness, connectors and storage. As of joins now clean both tables by the watermarks of both sides, Iceberg V3 compaction is applied with barriers, and the primary key index gains bounded compaction planning. A mssql_query table function was added, Oracle heartbeat tables can initialize automatically, and Pulsar consumer termination is retried. Fixes include streaming sum outputting NULL when no non-NULL input remains, TTL rows expiring by the forwarded watermark, arrangement backfill forwarding buffered rows on a barrier, and CDC backfill recovering from snapshot read failures.

Week of October 5, 2026

What shipped

Why it matters

This week brings new capabilities for Pulsar and Iceberg users, and a set of fixes that affect correctness in everyday streaming work: sink output when a primary key changes, recovery during CDC startup, and planner behavior on indexes. Users running MySQL and SQL Server CDC should see more reliable recovery and schema handling. The bounded-memory sort buffer and explicit cache warm-up address resource behavior under load.

Changelog entry

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

Post for X

This week: Iceberg V3 as an independent job, native Pulsar Avro schemas, a bounded-memory sort buffer for the locality provider, explicit table cache warm-up, and fixes across CDC recovery, sink output on primary key changes, and streaming time travel.

Post for LinkedIn

This week in the project: Iceberg V3 can be maintained as an independent job in the meta service. Pulsar sources now support native Avro schemas, so they can infer columns and decode messages written with different schema versions. A bounded-memory sort buffer for the locality provider was added to mitigate join amplification, and table caches can now be warmed up explicitly. Iceberg ADLS file IO configuration is shared, and variant access paths are prebuilt. On the fix side, sinks keep the old primary key delete when an update changes the sink primary key, upstream rows of finished vnodes are forwarded after a backfill reschedule, SQL Server CDC validates table name casing, and time travel is rejected in streaming jobs.

Week of September 28, 2026

What shipped

Why it matters

This week focused on CDC source stability and resource cleanup, with improvements to PostgreSQL and SQL Server connection handling. Storage performance was enhanced through a Foyer upgrade, and object store listing reliability was fixed to properly handle metadata errors.

Changelog entry

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

Post for X

Weekly digest: improved CDC connection shutdown for PostgreSQL and SQL Server, upgraded storage cache library, fixed object store metadata error handling, and refactored checkpoint job coordination.

Post for LinkedIn

This week's RisingWave updates improve operational stability and performance. CDC sources now properly force-close PostgreSQL and SQL Server connections during shutdown, preventing thread hangs and resource leaks. Storage performance improved via Foyer 0.22.6 upgrade. Object store listing now correctly propagates metadata errors. Additional checkpoint job coordination improvements in the metadata layer.

Week of September 21, 2026

What shipped

Why it matters

Version 3.1.0 ships with new streaming capabilities including broadcast temporal joins and keyed changelog support. Multiple stability fixes and new connector features expand Risingwave's capabilities for CDC and data integration use cases.

Changelog entry

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

Post for X

Risingwave 3.1.0 is out. New: broadcast temporal joins, keyed changelog execution, Oracle CDC plumbing, Iceberg compaction health metrics. Plus stability fixes across streams and refresh handling.

Post for LinkedIn

Risingwave 3.1.0 is available. This release adds broadcast temporal join support for stream processing, keyed changelog planning and execution, and Oracle CDC connector plumbing. New Iceberg compaction health metrics are now exposed, and multiple stability improvements cover table refresh handling, MATCH_RECOGNIZE scans, and source privilege enforcement.

Week of September 14, 2026

What shipped

Why it matters

V3.0.4 release brings stability improvements to compaction, streaming recovery, and connector handling. Watermark propagation through over-window operators improves latency for window-based queries. Better authentication support for Google Pub/Sub and fixes for primary key ordering make connectors more reliable.

Changelog entry

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

Post for X

V3.0.4 shipped with compaction stability, watermark improvements in over-window queries, Google Pub/Sub ADC auth, and connector fixes for SQL Server primary keys.

Post for LinkedIn

V3.0.4 released with compaction group stabilization, watermark forwarding through over-window operators for reduced latency, Google Pub/Sub Application Default Credentials support, and SQL Server composite primary key ordering fixes.

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.