You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This tracker covers the internal row-binlog and Table Stream stack used by incremental computation, plus its MTMV integration. External CDC Streaming Jobs and general MTMV partition refresh or query-rewrite changes are out of scope unless they directly modify this stack.
FE-side (CCR) binlog is listed under "Adjacent work" below: it is a separate feature, but several correctness issues tracked here live in that code and are reported against the same stack.
The repository review has been refreshed through 2026-09-01. PR #61382 predates the original review window but is included because it is the Table Stream metadata and DDL foundation.
Status summary (2026-09-01)
Layer
Merged
Open / Draft
Assessment
Row binlog
23
7
Main path complete; remaining work is scheduling locality, partial update, and throughput.
Table Stream
17
6
Local and cloud paths complete; metadata lifecycle and DDL surface still have gaps.
MTMV incremental maintenance
0
1 draft
Implemented on a branch, but nothing has been merged. This is the critical path.
Per #66719, the branch already covers projection, filter, aggregate (COUNT/SUM/AVG/MIN/MAX, bitmap aggregates, expression arguments, bare GROUP BY), INNER/CROSS/LEFT OUTER/FULL OUTER joins, UNION ALL, subquery aliases, REFRESH MATERIALIZED VIEW ... INCREMENTAL/PARTITIONS, dry-run, automatic full-refresh fallback, chained IVM MTMV, ivm_use_full_keys, and regression tests under mtmv_p0/ivm.
The blocker is not implementation, it is reviewability and landing. A single PR of this size cannot be reviewed effectively, and this layer currently has no assigned reviewer.
17 correctness issues have no linked PR and no assignee.
The unowned correctness issues (#67091–#67094, #67096–#67108) were filed together on 2026-08-25 and are design-level defects rather than isolated bugs: BE restart recovery, replica repair and balancing, TSO boundary semantics, cloud publish/commit failure handling, leader/follower metadata divergence, and lock/scan target disagreement after RENAME or REPLACE TABLE. They need owners before they can be scheduled.
Correctness and compatibility checklist
DUP and supported UNIQUE KEY MOW table semantics are documented and tested.
Full update, partial update, delete, sequence column, hidden key, and schema-change paths are covered.
LSN/TSO ordering is deterministic across replicas and remains valid after clone and compaction.
Concurrent stream consumption either commits data and offsets together or fails without advancing offsets.
Snapshot, reset, and incremental reads agree at partition boundaries and after restart.
Binlog retention cannot silently invalidate an active stream or MTMV; stale state is observable and recoverable.
Unsupported plans fail clearly or use a documented full-refresh fallback.
Cloud-mode support or exclusion is explicit.
Upgrade, downgrade, rolling restart, backup/restore, and replication behavior is defined before general availability.
Description
This issue tracks the end-to-end incremental computation capability in Apache Doris.
The implementation is being built in three layers:
This tracker replaces the stale umbrella issue #57921 and incorporates the row-binlog foundation originally tracked by #61956.
Goals
Scope boundary
This tracker covers the internal row-binlog and Table Stream stack used by incremental computation, plus its MTMV integration. External CDC Streaming Jobs and general MTMV partition refresh or query-rewrite changes are out of scope unless they directly modify this stack.
FE-side (CCR) binlog is listed under "Adjacent work" below: it is a separate feature, but several correctness issues tracked here live in that code and are reported against the same stack.
The repository review has been refreshed through 2026-09-01. PR #61382 predates the original review window but is included because it is the Table Stream metadata and DDL foundation.
Status summary (2026-09-01)
Progress
Row binlog foundation
Merged — core path:
RowBinlogSegmentWriter. Supersedes [refactor](storage) Add a block transform chain before segment writers #64674.Merged — fixes:
array_aggstate serialization.Open:
Table Stream foundation
Merged — core path:
Merged — fixes:
StreamTableInfo.Open:
ALTER STREAM SET COMMENTandCANCEL ALTER STREAMare not supported. No owner.MTMV incremental maintenance
Corrected. The previous revision of this tracker stated that no MTMV implementation PR had been identified. That is no longer accurate:
Per #66719, the branch already covers projection, filter, aggregate (COUNT/SUM/AVG/MIN/MAX, bitmap aggregates, expression arguments, bare GROUP BY), INNER/CROSS/LEFT OUTER/FULL OUTER joins, UNION ALL, subquery aliases,
REFRESH MATERIALIZED VIEW ... INCREMENTAL/PARTITIONS, dry-run, automatic full-refresh fallback, chained IVM MTMV,ivm_use_full_keys, and regression tests undermtmv_p0/ivm.The blocker is not implementation, it is reviewability and landing. A single PR of this size cannot be reviewed effectively, and this layer currently has no assigned reviewer.
Adjacent work
Bug and correctness backlog
#65265 is the consolidated bug and test backlog. Current state:
The unowned correctness issues (#67091–#67094, #67096–#67108) were filed together on 2026-08-25 and are design-level defects rather than isolated bugs: BE restart recovery, replica repair and balancing, TSO boundary semantics, cloud publish/commit failure handling, leader/follower metadata divergence, and lock/scan target disagreement after RENAME or REPLACE TABLE. They need owners before they can be scheduled.
Correctness and compatibility checklist
Overlapping or superseded PRs
Exit criteria