[
https://issues.apache.org/jira/browse/CALCITE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248808#comment-16248808
]
Julian Hyde commented on CALCITE-1048:
--------------------------------------
I don't remember what exactly we planned to do to fix this case; at a minimum,
remove hacks such as the one you found.
Clearly RelMdMaxRowCount of a RelSubset should be the lowest max-row-count of
any relational expression in that subset. Each kind of metadata should have a
way of deriving a subset's value from the constituent rel values; in the case
of RelMdMaxRowCount the roll-up function is "min".
I think that will handle Sort+limit automatically, I fear that if you put it in
place it will cause some stack-overflow problems.
> Make metadata more robust
> -------------------------
>
> Key: CALCITE-1048
> URL: https://issues.apache.org/jira/browse/CALCITE-1048
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Following CALCITE-794, make metadata more robust and performant, so we can
> safely derive metadata from a large RelNode graph.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
