hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Newman (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HIVE-2373) Importing hive tables into hbase+hive requires a lot of work which often can be implied
Date Fri, 12 Aug 2011 22:31:31 GMT
Importing hive tables into hbase+hive requires a lot of work which often can be implied
---------------------------------------------------------------------------------------

                 Key: HIVE-2373
                 URL: https://issues.apache.org/jira/browse/HIVE-2373
             Project: Hive
          Issue Type: Improvement
            Reporter: Alex Newman
            Priority: Minor


The HiveQL way of creating a HBase table looks something like 
REATE TABLE bla(id_1 type_1, id_2 type_2..., id_n type_n)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf:id_2, cf:id_3") TBLPROPERTIES ("hbase.table.name"
= "blah");

But in most cases huge amounts of this can be assumed from the original table description.
In fact in most cases, especially ones when that data was imported from MySQL it is trivial
to generate at least one HBase backing for that data. I currently wrote a python script which
our users can use to make things simpler. Would anyone be interested in that script? Would
it make sense to make it easy from Hive? I hate to add reserved words so any suggestions are
welcome.

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

        

Mime
View raw message