geyanggang opened a new pull request, #13193:
URL: https://github.com/apache/gravitino/pull/13193
### What changes were proposed in this pull request?
- `DataSourceUtils`: verify the configured `jdbc-driver` class is loadable
from
the catalog classpath (via `Class.forName`, without initialization) before
the
DBCP2 pool is created. A missing driver now fails at catalog creation with
a
clear message naming the driver, instead of an opaque
`ClassNotFoundException`
surfaced lazily on the first connection.
- Added a unit test (`testMissingDriverGivesClearError`).
- Docs: clarified the MySQL and OceanBase catalog pages — which driver
artifact/version to obtain, where to place it, and (for OceanBase) that
either
the OceanBase or MySQL Connector/J driver works.
### Why are the changes needed?
Gravitino does not package these drivers; users install them themselves.
Without
this, a missing driver produces a confusing, wrapped `ClassNotFoundException`
late in the flow and never names the driver to install.
Fix: #13192
### Does this PR introduce any user-facing change?
Yes, a clearer error message when a JDBC catalog's driver is not installed,
and
updated MySQL/OceanBase docs. No behavior change when the driver is present.
### How was this patch tested?
`:catalogs:catalog-jdbc-common:test` (22 tests, incl. the new one) and
`spotlessJavaCheck` pass.
--
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]
