You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Ruben Q L (Jira)" <ji...@apache.org> on 2019/11/13 17:14:00 UTC
[jira] [Commented] (CALCITE-3487) Should not hard code
RelMetadataQuery class in VolcanoPlanner.isValid()
[ https://issues.apache.org/jira/browse/CALCITE-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973541#comment-16973541 ]
Ruben Q L commented on CALCITE-3487:
------------------------------------
Apparently, this change breaks unit tests with DEBUG enabled.
See https://issues.apache.org/jira/browse/CALCITE-2018?focusedCommentId=16973226&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16973226
> 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
> Assignee: Xiening Dai
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.22.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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)