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 04fa4af
Browse filesBrowse the repository at this point in the historyBrowse files
### What problem does this PR solve?
Issue Number: None
Related PR: #68196
Problem Summary: Database discovery and HMS CREATE events fold mode-1 names with Locale.ROOT, but lookup and DROP used the process default locale. On a Turkish-locale FE, remote I was cached as i while later lookup and DROP sought dotless ı, leaving the dropped object visible. Use one locale-independent fold for database discovery, event IDs, lookup, routing, and Paimon SDK invalidation. Separately, catalog-wide row-count generation state was retained after permanent DROP even when no count was loaded. Avoid allocating unused generations and release a dropped catalog generation without letting an outstanding old read recreate it.
### Release note
External database name lookup and cache invalidation are consistent across FE locale settings.
### Check List (For Author)
- Test: Unit Test: four related FE classes, 164 tests passed; full FE build and Checkstyle passed
- Behavior changed: Yes, external database case folding is locale independent and permanent catalog drop releases row-count generation state
- Does this need documentation: No
0 commit comments