[
https://issues.apache.org/jira/browse/HIVE-18395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318893#comment-16318893
]
Steve Yeom edited comment on HIVE-18395 at 1/9/18 6:47 PM:
-----------------------------------------------------------
Another viewpoint/reason why not using stats on a ACID/MM table is that
a reader/select statement can not have a snapshot isolation regarding "actual
data" and "stats on the Metastore".
Since update on the data and the stats on the Metastore is not single
transaction based and
also there is no mechanism to get consistent snapshot isolation view on stats
regarding the
actual data.
was (Author: steveyeom2017):
Another viewpoint/reason why not using stats on a ACID/MM table is that
a reader/select statement can not have a snapshot isolation regarding "actual
data" and "stats on the Metastore".
Since update on the data and the stats on the Metastore is not single
transaction based.
> Using stats for aggregates on Acid/MM is off even with
> "hive.compute.query.using.stats" is true.
> ------------------------------------------------------------------------------------------------
>
> Key: HIVE-18395
> URL: https://issues.apache.org/jira/browse/HIVE-18395
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Steve Yeom
> Priority: Minor
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
