You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Mostafa Mokhtar (JIRA)" <ji...@apache.org> on 2015/01/15 21:41:35 UTC
[jira] [Updated] (HIVE-9392) JoinStatsRule miscalculates join
cardinality as incorrect NDV is used due to column names having duplicated
fqColumnName
[ https://issues.apache.org/jira/browse/HIVE-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mostafa Mokhtar updated HIVE-9392:
----------------------------------
Summary: JoinStatsRule miscalculates join cardinality as incorrect NDV is used due to column names having duplicated fqColumnName (was: Hive : JoinStatsRule overwrites the column statistics in HashMap because column names have duplicate fqColumnName)
> JoinStatsRule miscalculates join cardinality as incorrect NDV is used due to column names having duplicated fqColumnName
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-9392
> URL: https://issues.apache.org/jira/browse/HIVE-9392
> Project: Hive
> Issue Type: Bug
> Components: Physical Optimizer
> Affects Versions: 0.14.0
> Reporter: Mostafa Mokhtar
> Assignee: Prasanth Jayachandran
> Priority: Critical
> Fix For: 0.15.0
>
>
> In JoinStatsRule.process the join column statistics are stored in HashMap joinedColStats, the key used which is the ColStatistics.fqColName is duplicated between join column in the same vertex, as a result distinctVals ends up having duplicated values which negatively affects the join cardinality estimation.
> The duplicate keys are usually named KEY.reducesinkkey0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)