Ruben Q L created CALCITE-7908:
----------------------------------
Summary: ModelHandler should apply the model class-name filter to
the JDBC driver auto-detected from jdbcUrl
Key: CALCITE-7908
URL: https://issues.apache.org/jira/browse/CALCITE-7908
Project: Calcite
Issue Type: Task
Components: core
Reporter: Ruben Q L
Assignee: Ruben Q L
Fix For: 1.43.0
When a JDBC schema in a model file omits {{jdbcDriver}}, the driver class is
chosen automatically from {{jdbcUrl}} at connection time.
{{ModelHandler.visit(JsonJdbcSchema)}} calls
{{classNameFilter.check(jsonSchema.jdbcDriver)}}, which is a no-op when
{{jdbcDriver}} is null, so the auto-detected driver class is never validated
against the filter configured by {{calcite.model.classes.allowed}} /
{{calcite.model.classes.denied}} (CALCITE-7713).
As a result, the filter only governs schemas whose model explicitly names a
driver class. A schema that relies on driver auto-detection is loaded without
any class-name check, which is inconsistent with the explicit-driver path and
with the other entry points that the filter covers.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
