[
https://issues.apache.org/jira/browse/HIVE-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863746#comment-13863746
]
Nick Dimiduk commented on HIVE-3211:
------------------------------------
Please have a look at HBASE-10091. I don't know if the mapping can be
automatically detected, but I think HBase can provide a reasonable type
description language for users.
> Enhance hbase column mapping strategy to support complicated structures
> -----------------------------------------------------------------------
>
> Key: HIVE-3211
> URL: https://issues.apache.org/jira/browse/HIVE-3211
> Project: Hive
> Issue Type: Improvement
> Components: HBase Handler
> Affects Versions: 0.9.0
> Reporter: Swarnim Kulkarni
> Assignee: Swarnim Kulkarni
>
> With the current Hive-HBase integration, we need to specify the
> "hbase.columns.mapping" property that maps the hbase columns to the columns
> in hive. So for example,
> hive> CREATE EXTERNAL TABLE complex(
> key string,
> s struct<col1 : int, col2 : int>)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES (
> "hbase.columns.mapping" = ":key,cf:a"
> )TBLPROPERTIES ("hbase.table.name" = "TEST_TABLE");;
> The struct definition in the above query can quickly get very ugly if we are
> dealing with a very complicated structures stored in hbase columns. We should
> probably enhance the current columns mapping strategy to be able to provide a
> custom serializer and let it detect the structure by itself.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
