[
https://issues.apache.org/jira/browse/HIVE-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299596#comment-14299596
]
Daisy.Yuan commented on HIVE-9452:
----------------------------------
When one table has thousands columns, the bottleneck is in querying it from
meta store, and serialization and deserialization.
will it solve the second problem?
And what is like the schema of the meta store? What the row key in actual HBase
table.
When I drop the table with thousands columns, is it cause HBase split?
> Use HBase to store Hive metadata
> --------------------------------
>
> Key: HIVE-9452
> URL: https://issues.apache.org/jira/browse/HIVE-9452
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Reporter: Alan Gates
> Assignee: Alan Gates
>
> This is an umbrella JIRA for a project to explore using HBase to store the
> Hive data catalog (ie the metastore). This project has several goals:
> # The current metastore implementation is slow when tables have thousands or
> more partitions. With Tez and Spark engines we are pushing Hive to a point
> where queries only take a few seconds to run. But planning the query can
> take as long as running it. Much of this time is spent in metadata
> operations.
> # Due to scale limitations we have never allowed tasks to communicate
> directly with the metastore. However, with the development of LLAP this
> requirement will have to be relaxed. If we can relax this there are other
> use cases that could benefit from this.
> # Eating our own dogfood. Rather than using external systems to store our
> metadata there are benefits to using other components in the Hadoop system.
> The proposal is to create a new branch and work on the prototype there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
