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 2014/09/04 18:45:52 UTC

[jira] [Updated] (OPTIQ-362) Make non-cumulative cost (NonCumulativeCost) a pluggable form of metadata

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

Julian Hyde updated OPTIQ-362:
------------------------------
    Fix Version/s: 0.8

> Make non-cumulative cost (NonCumulativeCost) a pluggable form of metadata
> -------------------------------------------------------------------------
>
>                 Key: OPTIQ-362
>                 URL: https://issues.apache.org/jira/browse/OPTIQ-362
>             Project: Optiq
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>             Fix For: 0.8
>
>
> Non-cumulative cost, the cost of a RelNode not including its children is also known as RelNode.computeSelfCost(RelOptPlanner) and BuiltInMetadata.NonCumulativeCost.
> NonCumulativeCost should be included in the default metadata provider. (See how BuiltInMetadata.Selectivity is included via RelMdSelectivity.SOURCE.)
> Then people could add a different cost model for the core rel nodes (FilterRel, JoinRel etc.)



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