[
https://issues.apache.org/jira/browse/HIVE-11786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chaoyu Tang updated HIVE-11786:
-------------------------------
Attachment: HIVE-11786.1.patch
Reattached the patch to kick off another round of precommit tests since the
test failures look to me not related to the patch.
These failed tests are most TestMiniSparkOnYarnCliDriver tests and has a common
cause like:
==
2015-09-18 15:21:07,237 INFO [stdout-redir-1] client.SparkClientImpl
(SparkClientImpl.java:run(588)) - java.io.IOException: Failed to create local
dir in
/tmp/spark-01dba71e-0baf-473a-9fec-977803eac958/blockmgr-b5ff096e-b567-497d-94ee-a78bdf96cf31/32.
2015-09-18 15:21:07,237 INFO [stdout-redir-1] client.SparkClientImpl
(SparkClientImpl.java:run(588)) - at
org.apache.spark.storage.DiskBlockManager.getFile(DiskBlockManager.scala:73)
==
In addition, I was not able to reproduce the tests in my local machine.
The tests (MiniMR tests index_bitmap3.q, stats_counter_partitioned.q) initially
failed in 1st round of precommit tests did not fail in this round.
> Deprecate the use of redundant column in colunm stats related tables
> --------------------------------------------------------------------
>
> Key: HIVE-11786
> URL: https://issues.apache.org/jira/browse/HIVE-11786
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Chaoyu Tang
> Assignee: Chaoyu Tang
> Attachments: HIVE-11786.1.patch, HIVE-11786.1.patch, HIVE-11786.patch
>
>
> The stats tables such as TAB_COL_STATS, PART_COL_STATS have redundant columns
> such as DB_NAME, TABLE_NAME, PARTITION_NAME since these tables already have
> foreign key like TBL_ID, or PART_ID referencing to TBLS or PARTITIONS.
> These redundant columns violate database normalization rules and cause a lot
> of inconvenience (sometimes difficult) in column stats related feature
> implementation. For example, when renaming a table, we have to update
> TABLE_NAME column in these tables as well which is unnecessary.
> This JIRA is first to deprecate the use of these columns at HMS code level. A
> followed JIRA is to be opened to focus on DB schema change and upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
