[
https://issues.apache.org/jira/browse/CALCITE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesus Camacho Rodriguez updated CALCITE-995:
--------------------------------------------
Description:
CALCITE-987 introduced the RelMdMaxRowCount metadata provider. By default,
RelMdMaxRowCount returns Double.MAX, which is causing some infinite loops in
the current test suite, as Sort will continue being pushed below Union/Join (if
the estimate row count for Union/Join is Double.MAX).
I propose to return null by default if we cannot get the maximum number of
rows, which makes more sense and allows catching this issue.
was:
CALCITE-987 introduced the RelMdMaxRowCount metadata provider. By default,
RelMdMaxRowCount returns Double.MAX, which is causing some infinite loops in
the current test suite, as Sort will continue being pushed below Union/Join (if
the estimate row count for Union/Join is Double.MAX).
I propose to return null by default, which makes more sense.
> Sort transpose rules might fall in an infinite loop
> ---------------------------------------------------
>
> Key: CALCITE-995
> URL: https://issues.apache.org/jira/browse/CALCITE-995
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.6.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
>
> CALCITE-987 introduced the RelMdMaxRowCount metadata provider. By default,
> RelMdMaxRowCount returns Double.MAX, which is causing some infinite loops in
> the current test suite, as Sort will continue being pushed below Union/Join
> (if the estimate row count for Union/Join is Double.MAX).
> I propose to return null by default if we cannot get the maximum number of
> rows, which makes more sense and allows catching this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
