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
[Table Stream] Stream locking still uses the old base-table name after RENAME #67102
[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.
changed the title [-][Table Stream] 基表 RENAME 后 Stream 仍按旧表名加锁[/-][+][Table Stream] Stream locking still uses the old base-table name after RENAME[/+]on Aug 25, 2026
Activity
[-][Table Stream] 基表 RENAME 后 Stream 仍按旧表名加锁[/-][+][Table Stream] Stream locking still uses the old base-table name after RENAME[/+]morrySnow commentedon Sep 8, 2026
i don't think this is a bug, because the stream is bind on a table name, not a table object