[
https://issues.apache.org/jira/browse/OPTIQ-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved OPTIQ-362.
-------------------------------
Resolution: Fixed
This worked already.
There isn't a {{class RelMdNonCumulativeCost}}, but {{class
RelMdPercentageOriginalRows}} has a {{getCumulativeCost(RelNode)}} method and
registers its singleton as a source of {{interface NonCumulativeCost}} metadata
(and also of {{interface PercentageOriginalRows}} and {{interface
CumulativeCost}} metadata).
I haven't tried it, but it should be possible to register a provider with
methods such as {{getCumulativeCost(MyFilterRel)}}.
> 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
>
> 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)
