You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Ruben Q L (Jira)" <ji...@apache.org> on 2020/09/05 09:36:00 UTC
[jira] [Resolved] (CALCITE-4208) Improve metadata row count for
Join
[ https://issues.apache.org/jira/browse/CALCITE-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruben Q L resolved CALCITE-4208.
--------------------------------
Resolution: Fixed
Fixed via https://github.com/apache/calcite/commit/7353fa94bad8d5db48a217799d8c9567c9639a2f
> Improve metadata row count for Join
> -----------------------------------
>
> Key: CALCITE-4208
> URL: https://issues.apache.org/jira/browse/CALCITE-4208
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Ruben Q L
> Assignee: Ruben Q L
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.26.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Currently, the default metadata row count for join {{RelMdRowCount#getRowCount(Join rel, RelMetadataQuery mq)}} relies on {{RelMdUtil.getJoinRowCount}}. This method has several issues:
> - In case of ANTI join, it returns the same estimation as a SEMI join
> - In other cases (INNER, LEFT, RIGHT, FULL), it returns always the same formula:
> {{leftRowCount * rightRowCount * mq.getSelectivity(join, condition)}}
> which seems valid for an INNER join, but not for LEFT / RIGHT / FULL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)