You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/21 12:12:00 UTC

[jira] [Updated] (FLINK-6516) using real row count instead of dummy row count when optimizing plan

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

ASF GitHub Bot updated FLINK-6516:
----------------------------------
    Labels: pull-request-available  (was: )

> using real row count instead of dummy row count when optimizing plan
> --------------------------------------------------------------------
>
>                 Key: FLINK-6516
>                 URL: https://issues.apache.org/jira/browse/FLINK-6516
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>            Reporter: godfrey he
>            Assignee: godfrey he
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, the statistic of {{TableSourceTable}} is {{UNKNOWN}} mostly, and the statistic from {{ExternalCatalog}} maybe is null also. Actually, only each {{TableSource}} knows its statistic exactly, especial for {{FilterableTableSource}} and {{PartitionableTableSource}}. So we can add {{getTableStats}} method in {{TableSource}}, and use it in TableSourceScan's estimateRowCount method to get real row count.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)