[
https://issues.apache.org/jira/browse/HIVE-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341711#comment-16341711
]
Aihua Xu commented on HIVE-18366:
---------------------------------
I reverted this change since it's not necessary to make such change which will
cause backward incompatible. We just need a fix in HIVE-18550 to fix an
existing hive bug.
> Update HBaseSerDe to use hbase.mapreduce.hfileoutputformat.table.name instead
> of hbase.table.name as the table name property
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-18366
> URL: https://issues.apache.org/jira/browse/HIVE-18366
> Project: Hive
> Issue Type: Sub-task
> Components: HBase Handler
> Affects Versions: 3.0.0
> Reporter: Aihua Xu
> Assignee: Aihua Xu
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18366.1.patch, HIVE-18366.2.patch
>
>
> HBase 2.0 changes the table name property to
> hbase.mapreduce.hfileoutputformat.table.name. HiveHFileOutputFormat is using
> the new property name while HiveHBaseTableOutputFormat is not. If we create
> the table as follows, HiveHBaseTableOutputFormat is used which still uses the
> old property hbase.table.name.
> {noformat}
> create table hbase_table2(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')
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
