hussain-s opened a new pull request, #13876: URL: https://github.com/apache/gravitino/pull/13876
### What changes were proposed in this pull request? Allow the Flink JDBC catalog to initialize when `flink.bypass.default-database` is not configured. Fully qualified table references continue to resolve through Gravitino, while operations requiring a native default-database-backed JDBC catalog return a clear error. Statistics requests return `UNKNOWN` when no default database is configured. Add unit coverage for the no-default-database behavior and a Docker-backed MySQL integration test for a fully qualified query. ### Why are the changes needed? Flink previously rejected JDBC catalogs without `flink.bypass.default-database`, even when queries specified the complete `catalog.schema.table` path. This change supports MySQL catalogs without a default database as requested. Fix: #13798 ### Does this PR introduce _any_ user-facing change? Yes. Flink users can now use Gravitino JDBC/MySQL catalogs without configuring `flink.bypass.default-database` when they use fully qualified table names. Operations that require a default database now fail with a clear message. ### How was this patch tested? - Added common unit coverage for opening without a default database, `UNKNOWN` statistics, and the clear default-dependent error path. - Ran the focused JDBC catalog tests across Flink 1.19, 1.20, 2.1, and 2.2 (five tests passed on each). - Ran the Docker-backed Flink 1.20 MySQL regression test `FlinkJdbcMysqlCatalogIT120.testSelectFullyQualifiedTableWithoutDefaultDatabase`. -- 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]
