Problem
[Table Stream] Stream locking still uses the old base-table name after RENAME
Minimal reproduction path
Create a base table and Table Stream, rename the base table, then query the stream and inspect its metadata lock target. Repeat after a frontend restart or journal replay. Verify that locking and scanning follow the table identity rather than a stale table name.
Expected result
Rename does not leave stream locking on the old name or scanning an unintended object.
Source
This report is a sanitized tracking record for Jira DORIS-28086. Internal hosts, paths, artifacts, build identifiers, and private logs are intentionally omitted.
Problem
[Table Stream] Stream locking still uses the old base-table name after RENAME
Minimal reproduction path
Create a base table and Table Stream, rename the base table, then query the stream and inspect its metadata lock target. Repeat after a frontend restart or journal replay. Verify that locking and scanning follow the table identity rather than a stale table name.
Expected result
Rename does not leave stream locking on the old name or scanning an unintended object.
Source
This report is a sanitized tracking record for Jira DORIS-28086. Internal hosts, paths, artifacts, build identifiers, and private logs are intentionally omitted.