linliu-code opened a new pull request, #20236: URL: https://github.com/apache/hudi/pull/20236
### Describe the issue this Pull Request addresses closes #20235 A fully qualified read of a table whose `hoodie.properties` has no `hoodie.database.name` fails in planning when the session catalog throws while resolving the database that `HoodieFileIndex` guessed from the session. ### Summary and Changelog `HoodieFileIndex.getConfigProperties` now skips the best-effort catalog properties merge with a WARN when the database is guessed and the catalog lookup throws. When the database is recorded in `hoodie.properties`, the lookup is unchanged and still fails loudly. - `HoodieFileIndex.getConfigProperties`: the guessed-database lookup (including `currentDatabase`) runs inside `try`/`catch NonFatal`. - `TestHoodieFileIndex`: one test for the guessed-database case (fails without the fix), one pinning that a recorded database still propagates the catalog error. ### Impact Only reads that fail today change: they now succeed without the catalog properties merge. No public API or config change. ### Risk Level low. The guard applies only to the guessed-database case, where the merge is already best-effort. ### Documentation Update none ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [x] Adequate tests were added if applicable -- 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]
