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
{{ message }}
Repository navigation
Commit 7c47b53
Browse filesBrowse the repository at this point in the historyBrowse files
[feature](cloud) Support Cloud Table Stream control plane
### What problem does this PR solve?
Issue Number: closeapache#65418
Related PR: apache#65810
Problem Summary: Table Stream keeps per-partition consumption offsets in FE for storage-compute integrated deployments. In Cloud mode, target-table transactions are committed by MetaService, so FE-owned offsets cannot be advanced atomically with target data. This change adds the Cloud Table Stream control plane, stores Latest and Versioned offsets in MetaService, reuses the Index and recycler lifecycle, resolves statement-level read snapshots through clone chains, and commits expected-offset CAS updates with target data in the same immediate FDB transaction. It also integrates the Row Binlog commit TSO contract, initializes empty-partition TSO metadata, and waits for pending lazy publish using the actual clone-chain owner before rereading the complete snapshot.
### Release note
Add the storage-compute separated Table Stream control plane.
### Check List (For Author)
- Test:
- Unit Test: Cloud Table Stream 28/28, CloneChainReader 25/25, empty partition TSO initialization 1/1, FE Cloud Stream 26/26
- Behavior changed: Yes. Cloud Table Stream uses MetaService-managed offsets and immediate atomic consumption commits while preserving non-Cloud behavior.
- Does this need documentation: Yes. The implementation and test designs have been updated.
0 commit comments