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

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/03/02 21:31:04 UTC

[jira] [Resolved] (CALCITE-607) Change visibility of constructor in metadata providers for size, memory, parallelism

     [ https://issues.apache.org/jira/browse/CALCITE-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-607.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0-incubating

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/b659d0f3.

Note that you can chain metadata providers. So, you could create say HiveRelMdMemory, a metadata provider that implements methods for Hive relational expressions, and chain it with RelMdMemory, the metadata provider that implements the core relational expressions.

However, sub-classing is also reasonable, so I am accepting this pull request.

> Change visibility of constructor in metadata providers for size, memory, parallelism
> ------------------------------------------------------------------------------------
>
>                 Key: CALCITE-607
>                 URL: https://issues.apache.org/jira/browse/CALCITE-607
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>             Fix For: 1.1.0-incubating
>
>




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