[
https://issues.apache.org/jira/browse/CALCITE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246869#comment-16246869
]
Aman Sinha commented on CALCITE-1048:
-------------------------------------
The comments in RelMdMaxRowCount point to this JIRA:
{noformat}
public Double getMaxRowCount(RelSubset rel, RelMetadataQuery mq) {
// FIXME This is a short-term fix for [CALCITE-1018]. A complete
// solution will come with [CALCITE-1048].
Util.discard(Bug.CALCITE_1048_FIXED);
...
}
{noformat}
It seems the goal of this JIRA is much broader and I am not sure of its status.
For the RelSubset's max row count, should we consider adding specific
implementations similar to what was done for CALCITE-1018 (for sort with limit)
? For example, if the RelSubset contains Aggregate with no group-by it will
have a max rowcount of 1.
> 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)
