[
https://issues.apache.org/jira/browse/CALCITE-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032784#comment-15032784
]
Julian Hyde edited comment on CALCITE-987 at 12/1/15 12:25 AM:
---------------------------------------------------------------
[~pxiong] and [~jcamachorodriguez], Please review
https://github.com/julianhyde/calcite/tree/987-max-row-count. I believe I've
fixed the above issues.
was (Author: julianhyde):
Please see further discussion in CALCITE-995.
> Push limit 0 will result in an infinite loop
> --------------------------------------------
>
> Key: CALCITE-987
> URL: https://issues.apache.org/jira/browse/CALCITE-987
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.0
> Reporter: Pengcheng Xiong
> Assignee: Pengcheng Xiong
> Fix For: 1.6.0
>
> Attachments: CALCITE-987.01.patch, CALCITE-987.02.patch,
> CALCITE-987.03.patch, CALCITE-987.04.patch
>
>
> We use "checkInputForCollationAndLimit" in RelMdUtil.java to check the input
> #rows. However, it calls RelMetadataQuery.getRowCount which will validate the
> #rows. The validation will change #row=0 to #row=1. This will result in an
> infinite loop to push limit. The affected rules include
> SortUnionTransposeRule and any Sort***TransposeRules that call
> checkInputForCollationAndLimit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
