You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2019/02/22 00:01:00 UTC

[jira] [Assigned] (IMPALA-8033) PlanNode getInputCardinality has two conflicting meanings

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

Paul Rogers reassigned IMPALA-8033:
-----------------------------------

    Assignee:     (was: Paul Rogers)

> PlanNode getInputCardinality has two conflicting meanings
> ---------------------------------------------------------
>
>                 Key: IMPALA-8033
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8033
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 3.1.0
>            Reporter: Paul Rogers
>            Priority: Minor
>
> The use of the method {{PlanNode.getInputCardinality()}} has evolved to have two slightly different, but conflicting, meanings:
> * The actual cardinality of the input table, needed to compute join cardinality.
> * The number of rows to be read, taking into consideration any limits placed on reading.
> Because join calculations are wrong if we do not use the actual base table cardinality, we cannot use the input cardinality interchangeably with table cardinality.
> Instead, break the function into two: {{getTableCardinality()}} to get the actual cardinality for use in joins, and the existing {{getInputCardinality()}} used for other purposes.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org