924060929 opened a new pull request, #69806: URL: https://github.com/apache/doris/pull/69806
### What problem does this PR solve? Related PR: #69501, #69629, #69632 Problem Summary: External metadata reads can discover a dropped table after resolving a cached handle. Fresh Hive SHOW CREATE, table comments, and view/schema reads did not all reach guarded lookup cleanup. A refreshed names list could also omit an old object that remained resident. In case-folding modes, targeted cleanup cleared unrelated numeric ID routes, preventing background callers from reloading surviving tables by ID. Route confirmed provider absence through one typed SPI exception carrying the remote database/table identity. Reuse the existing FE observation and generation guards for cleanup, preserving current replacements, live views, and session bypasses. Keep HMS exception wrapping and comment display fallbacks. Missing files, permission/transport errors, and other resources do not authorize cleanup. Retire only the target's ROOT-folded ID aliases while retaining unrelated routes. Ordinary writes remain metadata-only. The new shared exception contract bumps the connector plugin API to 26.0; no cache owner or persisted ID format changes. ### Release note Repair stale external-table lookup state after confirmed table or view absence while preserving same-name replacements and unrelated numeric lookups. ### Check List (For Author) - Test: Unit Test - 266 unique cases passed across the connector SPI suite, HMS/Hive/Iceberg adapter tests, and focused FE cache, refresh, and concurrency tests. Three new cases failed on the original behavior. FE build and Checkstyle passed with UI disabled. One FE startup port collision was diagnosed and the affected class rerun successfully. Providers are controlled fakes; no live external-service integration claim. - Behavior changed: Yes - complete guarded cleanup for confirmed absence and preserve sibling ID routes during targeted wide invalidation. - Does this need documentation: No -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
