geyanggang opened a new issue, #13192:
URL: https://github.com/apache/gravitino/issues/13192
### What would you like to be improved?
Gravitino does not package several JDBC drivers (e.g. MySQL Connector/J,
OceanBase), so users install them into `catalogs/<provider>/libs` themselves.
When the driver is absent, the catalog does not fail at creation time.
Instead,
DBCP2 loads the driver lazily, so the failure only surfaces on the first
operation and as an opaque, wrapped `ClassNotFoundException` ("Cannot load
JDBC
driver class ...") — it does not clearly tell the user which driver to
install.
### How should we improve?
- Verify the configured `jdbc-driver` class is on the catalog classpath when
the
data source is built, so catalog creation fails fast.
- Return a clear, actionable message naming the missing driver class and
telling
the user to install the driver JAR, instead of a raw
`ClassNotFoundException`.
- While here, clarify the MySQL and OceanBase catalog docs on which driver
artifact/version to obtain and where to place it (OceanBase accepts either
the
OceanBase or MySQL Connector/J driver, as it speaks the MySQL wire
protocol).
--
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]
