You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Laljo John Pullokkaran (JIRA)" <ji...@apache.org> on 2015/09/25 20:57:04 UTC
[jira] [Commented] (HIVE-11964) RelOptHiveTable.hiveColStatsMap
might contain mismatched column stats
[ https://issues.apache.org/jira/browse/HIVE-11964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908520#comment-14908520 ]
Laljo John Pullokkaran commented on HIVE-11964:
-----------------------------------------------
[~ctang.ma] Please see the comments on RB
> RelOptHiveTable.hiveColStatsMap might contain mismatched column stats
> ---------------------------------------------------------------------
>
> Key: HIVE-11964
> URL: https://issues.apache.org/jira/browse/HIVE-11964
> Project: Hive
> Issue Type: Bug
> Components: Query Planning, Statistics
> Affects Versions: 1.2.1
> Reporter: Chaoyu Tang
> Assignee: Chaoyu Tang
> Attachments: HIVE-11964.patch
>
>
> RelOptHiveTable.hiveColStatsMap might contain mismatched stats since it was built by assuming the stats returned from
> ==
> hiveColStats =StatsUtils.getTableColumnStats(hiveTblMetadata, hiveNonPartitionCols, nonPartColNamesThatRqrStats);
> or
> HiveMetaStoreClient.getTableColumnStatistics(dbName, tableName, colNames)
> ==
> have the same order of the requested columns. But actually the order is non-deterministic. therefore the returned stats should be re-ordered before it is put in hiveColStatsMap.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)