hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Lehuen (JIRA)" <>
Subject [jira] [Commented] (HIVE-6308) COLUMNS_V2 Metastore table not populated for tables created without an explicit column list.
Date Wed, 23 Jul 2014 06:40:39 GMT


Julien Lehuen commented on HIVE-6308:

This is *critical* for Impala users! We want to be able to perform our Metastore operations
via Hive's Thrift server, but this would create unhealthy tables for which we can not run
ANALYZE. Such table's statistics cannot computed by Impala (statistics are absolutely necessary
for Impala to run joins in an optimal manner), and this means that we need to create table
via Impala over JDBC. This is less than ideal, and this issue is the only blocker from letting
us create via Hive over Thrift.

Related IMPALA tickets: [IMPALA-867|], [IMPALA-1104|]

> COLUMNS_V2 Metastore table not populated for tables created without an explicit column
> --------------------------------------------------------------------------------------------
>                 Key: HIVE-6308
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Database/Schema
>    Affects Versions: 0.10.0
>            Reporter: Alexander Behm
> Consider this example table:
> CREATE TABLE avro_test
> 'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
> ''
> ''
> 'avro.schema.url'='file:///path/to/the/schema/test_serializer.avsc');
> When I try to run an ANALYZE TABLE for computing column stats on any of the columns,
then I get:
> org.apache.hadoop.hive.ql.metadata.HiveException: NoSuchObjectException(message:Column
o_orderpriority for which stats gathering is requested doesn't exist.)
>     at org.apache.hadoop.hive.ql.metadata.Hive.updateTableColumnStatistics(
>     at org.apache.hadoop.hive.ql.exec.ColumnStatsTask.persistTableStats(
>     at org.apache.hadoop.hive.ql.exec.ColumnStatsTask.execute(
>     at org.apache.hadoop.hive.ql.exec.Task.executeTask(
>     at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(
>     at org.apache.hadoop.hive.ql.Driver.launchTask(
>     at org.apache.hadoop.hive.ql.Driver.execute(
>     at
>     at
>     at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(
>     at org.apache.hadoop.hive.cli.CliDriver.processCmd(
>     at org.apache.hadoop.hive.cli.CliDriver.processLine(
>     at
>     at org.apache.hadoop.hive.cli.CliDriver.main(
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>     at java.lang.reflect.Method.invoke(
>     at org.apache.hadoop.util.RunJar.main(
> The root cause appears to be that the COLUMNS_V2 table in the Metastore isn't populated
properly during the table creation.

This message was sent by Atlassian JIRA

View raw message