[jira] [Created] (CALCITE-1262) Only one set of JDBC rules fire when multiple conventions are used due to static rule descriptions

["Jordan Halterman (JIRA)" <ji...@apache.org>]

Jordan Halterman created CALCITE-1262:
-----------------------------------------

             Summary: Only one set of JDBC rules fire when multiple conventions are used due to static rule descriptions
                 Key: CALCITE-1262
                 URL: https://issues.apache.org/jira/browse/CALCITE-1262
             Project: Calcite
          Issue Type: Bug
          Components: core
            Reporter: Jordan Halterman
            Assignee: Julian Hyde


When scans of multiple JDBC tables with separate {{JdbcConvention}}s are included in the same logical plan, {{VolcanoPlanner}} only fires rules for one of the conventions. This results in only one of the databases benefiting from optimizations and forces only {{JdbcToEnumerableConverter}} over {{JdbcTableScan}} in the other. This seems to be a result of static rule descriptions in all JDBC rules except {{JdbcToEnumerableConverterRule}}. When JDBC rule descriptions are changed to include the {{JdbcConvention}}, all rules are fired as expected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)