[
https://issues.apache.org/jira/browse/HIVE-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281156#comment-16281156
]
Naveen Gangam commented on HIVE-18202:
--------------------------------------
[~aihuaxu] I do not have the full context to the hbase side changes in 2.0, but
I was wondering if we should add a new row with the new property for every
table that has that property? Would HBase care if it had both the properties?
If it does not care, then it would make this change backward compatible too in
case the schema has to be rolled back for any reason.
Currently, with this proposed fix, I am worried that we are making not work
with the old release anymore.
> Automatically migrate hbase.table.name to
> hbase.mapreduce.hfileoutputformat.table.name for hbase-based table
> ------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-18202
> URL: https://issues.apache.org/jira/browse/HIVE-18202
> Project: Hive
> Issue Type: Sub-task
> Components: HBase Handler
> Affects Versions: 3.0.0
> Reporter: Aihua Xu
> Assignee: Aihua Xu
> Attachments: HIVE-18202.1.patch
>
>
> The property name for Hbase table mapping is changed from hbase.table.name to
> hbase.mapreduce.hfileoutputformat.table.name in HBase 2.
> We can include such upgrade for existing hbase-based tables in DB upgrade
> script to automatically change such values.
> For the new tables, the query will be like:
> create table hbase_table(key int, val string) stored by
> 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' with serdeproperties
> ('hbase.columns.mapping' = ':key,cf:val') tblproperties
> ('hbase.mapreduce.hfileoutputformat.table.name' =
> 'positive_hbase_handler_bulk')
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
