hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anja Gruenheid (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1940) Query Optimization Using Column Metadata and Histograms
Date Sat, 05 Feb 2011 18:05:30 GMT

    [ https://issues.apache.org/jira/browse/HIVE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991022#comment-12991022
] 

Anja Gruenheid commented on HIVE-1940:
--------------------------------------

Here is the metastore model that I generated with MySQL Workbench: http://home.in.tum.de/~gruenhei/HiveMetaStore.pdf
Comparing this model to the one displayed in the index wiki, I noticed the two tables PARTITIONS
and PARTITION_KEY_VALS are missing in my model. Do you have any idea how I can create them?
I tried adding partitions on tables, but that just created entries in table PARTITION_KEYS.

> Query Optimization Using Column Metadata and Histograms
> -------------------------------------------------------
>
>                 Key: HIVE-1940
>                 URL: https://issues.apache.org/jira/browse/HIVE-1940
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore, Query Processor
>            Reporter: Anja Gruenheid
>
> The current basis for cost-based query optimization in Hive is information gathered on
tables and partitions. To make further improvements in query optimization possible, the next
step is to develop and implement possibilities to gather information on columns as discussed
in issue HIVE-33. After that, an implementation of histograms is a possible option to use
and collect run-time statistics. Next to the actual implementation of these features, it is
also necessary to develop a consistent storage model for the MetaStore.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message