diqiu50 opened a new issue, #13269:
URL: https://github.com/apache/gravitino/issues/13269
### What would you like to be improved?
When no `SparkCatalogExtension` serves a provider,
`CatalogNameAdaptor.getCatalogName` maps every `jdbc-*` provider (except
`jdbc-postgresql`) to the generic `GravitinoJdbcCatalogSpark3x` by prefix
match. A provider that needs a dedicated catalog from an extension jar
therefore registers silently with the generic one when that jar is missing, and
users only see type or DDL errors deep inside Spark.
Trino and Flink fail fast here, but their errors (`Unsupported catalog
provider jdbc-xxx.` / `Failed to correctly match the Flink catalog factory.`)
do not mention a possibly missing extension jar, and the Flink one omits the
provider name.
### How should we improve?
- Spark: replace the `startsWith("jdbc")` fallback with an explicit list of
providers the generic JDBC catalog supports; any other `jdbc-*` provider
without an extension should fail registration with a clear error.
- Flink/Trino: name the provider in the error and mention that it may be
served by a separate extension jar.
--
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]
