You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Haisheng Yuan (Jira)" <ji...@apache.org> on 2019/11/08 23:23:00 UTC

[jira] [Resolved] (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:all-tabpanel ]

Haisheng Yuan resolved CALCITE-3487.
------------------------------------
    Fix Version/s: 1.22.0
       Resolution: Fixed

Fixed in https://github.com/apache/calcite/commit/f90e5d7b48848191c1a70e6c0f78eece93433806.

> 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)