Repository navigation
[Binlog][Cloud] VISIBLE retry loses version outcome and permits stale read after Table Stream commit #67099
Description
Problem
[Binlog][Cloud] VISIBLE retry loses version outcome and permits stale read after Table Stream commit
Minimal reproduction path
In a Cloud Table Stream workload, make the response of a VISIBLE operation unavailable after the commit is durable and execute the retry path. Read the stream immediately after recovery and after a fresh metadata lookup. Verify that the retry returns the durable version outcome and never permits a stale read after the stream commit.
Expected result
VISIBLE retry reports the durable version and subsequent reads are not stale.
Source
This report is a sanitized tracking record for Jira DORIS-28072. Internal hosts, paths, artifacts, build identifiers, and private logs are intentionally omitted.
Activity
[chore](fe) Merge master and preserve cloud transaction tests
[refactor](cloud) Iterate transaction table IDs directly
[fix](cloud) Invalidate caches after visible commit retries
[test](cloud) Adapt version cache mocks to explicit retry limits
[fix](build) Restore Java plugin dependencies on Maven cache hits
[fix](build) Merge upstream Maven cache packaging repair
[fix](cloud) Invalidate version caches on visible commit retries (#67813
branch-incremental-computation: pick the merged incremental-computati…
branch-4.1: [fix](cloud) Invalidate version caches on visible commit …
branch-4.1: [fix](cloud) Invalidate version caches on visible commit …