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.
Attachments
Issue Links
- is broken by
-
CALCITE-987 Push limit 0 will result in an infinite loop
- Closed
- relates to
-
CALCITE-1018 SortJoinTransposeRule not firing due to getMaxRowCount(RelSubset) returning null
- Closed