fix: Handle hudi table reads when databaseName is not set during initTable

[vinishjail97]

Describe the issue this Pull Request addresses

Fixes an issue where Hudi tables fail to load with IllegalArgumentException: "is not a Hudi table" when hoodie.database.name is not set in the table config during initialization. This occurs because when both table.identifier.database and getCurrentDatabase are null/empty during table initialization, the database name is not defaulted to "default", causing inconsistent behavior between table creation and querying.

Summary and Changelog

Tables initialized without an explicit database name now correctly default to "default" database, preventing subsequent read failures.

Impact

No public API changes. This is an internal fix to ensure consistent behavior.

Risk Level

Low

Documentation Update

None.

Contributor's checklist

• Read through contributor's guide
• Enough context is provided in the sections above
• Adequate tests were added if applicable

[hudi-bot]

CI report:

• 7efc17b Azure: FAILURE

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build