[
https://issues.apache.org/jira/browse/CALCITE-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiening Dai updated CALCITE-3487:
---------------------------------
Description: With CALCITE-3446, a calcite user can choose to provide a
sub-class of RelMetadataQuery through RelOptCluster.setMetadataQuery(). We
cannot assume the base class RelMetadataQuery is always used in planner. (was:
With CALCITE-3446, a calcite user can choose to provide a customized provide a
sub-class of RelMetadataQuery through RelOptCluster.setMetadataQuery(). We
cannot assume the base class RelMetadataQuery is always used in planner.)
> Should not hard code RelMetadataQuery class in VolcanoPlanner.isValid()
> -----------------------------------------------------------------------
>
> Key: CALCITE-3487
> URL: https://issues.apache.org/jira/browse/CALCITE-3487
> Project: Calcite
> Issue Type: Bug
> Reporter: Xiening Dai
> Priority: Major
>
> With CALCITE-3446, a calcite user can choose to provide a sub-class of
> RelMetadataQuery through RelOptCluster.setMetadataQuery(). We cannot assume
> the base class RelMetadataQuery is always used in planner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)