Yukang-Lian opened a new pull request, #66743:
URL: https://github.com/apache/doris/pull/66743
### What problem does this PR solve?
Issue Number: N/A
Related PR: #65810, #65859
Problem Summary:
Cloud Row Binlog and Cloud Table Stream now have an integrated data and
control plane, but the Cloud SQL path and several cross-module correctness
boundaries did not have complete automated coverage.
This PR adds layered coverage for the four Table Stream flows:
- Create: batched Offset initialization, retries, partial-state cleanup,
empty and newly added partitions.
- Query: statement-level snapshots, initial/snapshot/reset reads,
clone-chain inheritance, partial responses, and read-only behavior.
- Update: Offset CAS, target-table atomicity, idempotent retry, multiple
Streams, immediate commit, size limits, and source publish concurrency.
- Delete: typed drop requests, partition identity propagation, operation-log
recovery, clone-safe GC, paginated cleanup, and instance deletion.
It also adds Cloud SQL suites for initial rows, repeated consumption,
explicit partitions, multiple references, partition lifecycle, schema changes,
metadata, and object lifecycle. A Docker specialty test verifies real FE
Catalog and MetaChecker orphan-Offset detection.
The expanded tests found and fix two operational validation issues:
malformed versioned set_value input now returns INVALID_ARGUMENT instead of
dereferencing a null protobuf, and check_instance now validates the typed
RecycleIndex binding/state before suppressing a transient projection gap.
### Release note
None
### Check List (For Author)
- Test: Regression test / Unit Test
- `NODE_OPTIONS=--openssl-legacy-provider DORIS_TOOLCHAIN=clang
./build.sh --fe -j80`
- `DORIS_TOOLCHAIN=clang ./build.sh --cloud -j80`
- FE Table Stream tests: 43/43 passed
- Cloud focused tests: 90/90 passed
- Cloud Table Stream SQL regression: 9/9 passed
- Docker `check_meta` integration: 1/1 passed
- Row Binlog regression: 12/12 passed
- Ordinary Cloud shared-path baselines: 6/6 passed
- Modified C++ format check and clang-tidy
- `git diff --check`
- Behavior changed: No
- Does this need documentation: No
Specialty boundaries that require destructive process/network fault
environments (real FE journal crash/replay, real FoundationDB network
partitions, and killing Recycler at every batch boundary) remain outside normal
P0 regression. Equivalent persisted-state and response-loss semantics are
covered deterministically by the added unit tests.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
