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 f80fa3b
Browse filesBrowse the repository at this point in the historyBrowse files
[fix](fe) Reuse Iceberg dictionary freshness per metadata generation
### What problem does this PR solve?
Issue Number: N/A
Related PR: #69299
Problem Summary: Repeated Iceberg dictionary freshness checks detach the latest snapshot by eagerly loading its partition view. When the partition entry is disabled, rejected by its weight limit or retired, three checks of the same immutable generation invoke the complete view loader three times. Use the existing scoped snapshot callback and retain only the exact maximum partition-update timestamp in that generation. A synchronized lazy getter computes it once, including an empty view's zero result; a new metadata generation computes its own value. Reserve the fixed scalar/flag fields in snapshot accounting and keep complete partition maps subject to the existing admission policy. Focused tests reduce three loader invocations to one without retaining an unadmitted full view; this is a loader-count result, not a latency benchmark.
### Release note
Avoid repeated partition metadata enumeration during Iceberg dictionary freshness checks.
### Check List (For Author)
- Test: Unit Test: 207 related FE tests; full FE packaging and Checkstyle via build.sh --fe
- Behavior changed: Yes; reuse the same freshness value within one immutable metadata generation without retaining full partition views
- Does this need documentation: No
0 commit comments