You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2017/03/21 17:55:41 UTC
[jira] [Comment Edited] (CALCITE-760) Aggregate recommender blows
up if row count estimate is too high
[ https://issues.apache.org/jira/browse/CALCITE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590658#comment-14590658 ]
Julian Hyde edited comment on CALCITE-760 at 3/21/17 5:54 PM:
--------------------------------------------------------------
Test case and workaround added in http://git-wip-us.apache.org/repos/asf/calcite/commit/e7d15add but issue is not fixed yet.
was (Author: julianhyde):
Test case and workaround added in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/e7d15add but issue is not fixed yet.
> Aggregate recommender blows up if row count estimate is too high
> ----------------------------------------------------------------
>
> Key: CALCITE-760
> URL: https://issues.apache.org/jira/browse/CALCITE-760
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> If you run the aggregate recommendation algorithm with a value of rowCountEstimate that is wrong and large, the algorithm runs for a long time and eventually fails with "OutOfMemoryError: GC overhead limit exceeded".
> I have added LatticeTest.testLatticeWithBadRowCountEstimate as a test case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)