Skip to content

[Binlog][Cloud] VISIBLE retry loses version outcome and permits stale read after Table Stream commit #67099

Description

@MoanasDaddyXu

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions