hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <>
Subject [jira] [Commented] (HIVE-2941) Hive should expand nested structs when setting the table schema from thrift structs
Date Wed, 30 May 2012 21:57:23 GMT


Ashutosh Chauhan commented on HIVE-2941:

+1 will commit if tests pass.
> Hive should expand nested structs when setting the table schema from thrift structs
> -----------------------------------------------------------------------------------
>                 Key: HIVE-2941
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Travis Crawford
>            Assignee: Travis Crawford
>         Attachments: HIVE-2941.D2721.1.patch
> When setting a table serde, the deserializer is queried for its schema, which is used
to set the metastore table schema. The current implementation uses the class name stored in
the field as the field type.
> By storing the class name as the field type, users cannot see the contents of a struct
with "describe tblname". Applications that query HiveMetaStore for the table schema (specifically
HCatalog in this case) see an unknown field type, rather than a struct containing known field
> Hive should store the expanded schema in the metastore so users browsing the schema see
expanded fields, and applications querying metastore see familiar types.
> Set the table serde to something like this. This serde uses the built-in {{ThriftStructObjectInspector}}.
> {code}
> alter table foo_test
>   set serde "com.twitter.elephantbird.hive.serde.ThriftSerDe"
>   with serdeproperties ("serialization.class"="");
> {code}
> This causes a call to {{MetaStoreUtils.getFieldsFromDeserializer}} which returns a list
of fields and their schemas. However, currently it does not handle nested structs, and if
{{}} above contains a field {{}}, the class name {{}} would
appear as the field type. Instead, nested structs should be expanded.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message