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
Commit 25d0c27
Browse filesBrowse the repository at this point in the historyBrowse files
[fix](stream) Track stream base dependencies by identity
### What problem does this PR solve?
Issue Number: closeapache#65418
Related PR: apache#66287
Problem Summary: Stream base tables are implicit planning dependencies resolved by stable table ID. Keeping them in the qualifier-keyed relation cache can overwrite an explicitly resolved relation after concurrent renames, while resolving them again during preload or locking can select a different object snapshot. MTMV relation generation also omitted the underlying stream base after it was removed from the relation cache. Store exact implicit dependency objects separately, reuse them for preload and locking, include them in all-level MTMV dependencies, and reject dropped tables during cache-miss recovery resolution.
### Release note
Streams continue to track and lock their original base tables by stable identity without corrupting explicit relation bindings.
### Check List (For Author)
- Test: Unit Test
- 43 FE tests passed across DropTableStreamTest, StatementContextTest, ExplainTableStreamPlanTest, and MTMVRelationTest
- StatementContextTest rerun: 11 tests passed
- Java compilation and Checkstyle passed
- Behavior changed: Yes. Stream base dependencies use a stable per-statement object snapshot for planning locks and MTMV dependency tracking.
- Does this need documentation: No
0 commit comments