[
https://issues.apache.org/jira/browse/HIVE-11852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941642#comment-14941642
]
Sushanth Sowmyan commented on HIVE-11852:
-----------------------------------------
[~ashutoshc], the problem with a config property here is that this stats squish
I'm trying to prevent does not happen on the ql-side. This happens on the
metastore, from the AlterTableHandler where an alter table gets issued from the
client side. The metastore then decides that since the table has been altered,
the table is now different, and thus, stats must be nuked.
I feel like if the decision to nuke the stats were not made by the metastore,
but by the ql-side, that is cleaner and would not result in this problem, but
then if stats squishing and table altering were two different metastore calls,
we run into issues where one succeeding and the other not would lead to
incorrect data elsewhere, apart from other performance implications as well.
> numRows and rawDataSize table properties are not replicated
> -----------------------------------------------------------
>
> Key: HIVE-11852
> URL: https://issues.apache.org/jira/browse/HIVE-11852
> Project: Hive
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 1.2.1
> Reporter: Paul Isaychuk
> Assignee: Sushanth Sowmyan
> Attachments: HIVE-11852.patch
>
>
> numRows and rawDataSize table properties are not replicated when exported for
> replication and re-imported.
> {code}
> Table drdbnonreplicatabletable.vanillatable has different TblProps from
> drdbnonreplicatabletable.vanillatable expected [{numFiles=1, numRows=2,
> totalSize=560, rawDataSize=440}] but found [{numFiles=1, totalSize=560}]
> java.lang.AssertionError: Table drdbnonreplicatabletable.vanillatable has
> different TblProps from drdbnonreplicatabletable.vanillatable expected
> [{numFiles=1, numRows=2, totalSize=560, rawDataSize=440}] but found
> [{numFiles=1, totalSize=560}]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
