You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Adam Kennedy (Jira)" <ji...@apache.org> on 2023/04/14 22:04:00 UTC

[jira] [Updated] (CALCITE-5647) RelMdPopulationSize directly calls rel.estimateRowCount instead of mq.getRowCount

     [ https://issues.apache.org/jira/browse/CALCITE-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Kennedy updated CALCITE-5647:
----------------------------------
    Summary: RelMdPopulationSize directly calls rel.estimateRowCount instead of mq.getRowCount  (was: RelMdPopulationSize directly calls rel.estimateRowCount instead mq.getRowCount)

> RelMdPopulationSize directly calls rel.estimateRowCount instead of mq.getRowCount
> ---------------------------------------------------------------------------------
>
>                 Key: CALCITE-5647
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5647
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.34.0
>            Reporter: Adam Kennedy
>            Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> A few locations in Calcite call rel.estimateRowCount(mq) when they should instead call mq.getRowCount(red).
> We detected this because we implemented row count estimation entirely within an alternative handle instead of RelMdRowCount, and then override estimateRowCount to ensure the custom handler is user, by throwing an unreachable code exception.
> A few places in Calcite trigger these unreachable exceptions because they do not use mq.getRowCount.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)