[IMPALA-587] Impala should handle malformatted HBase table mapping gracefully

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 1.0.1
• Fix Version/s: Impala 1.2
• Assignee: Lenni Kuff
• Reporter: Alan Choi
• Created: 10/Sep/13 20:38
• Updated: 20/Dec/15 00:05
• Resolved: 07/Oct/13 06:03

Description

If the column mapping does not match the schema, Impala does not handle it gracefully. In this example:

1) $hbase shell
hbase(main):002:0>create 'testtable','colfam1'
2) In Hive Shell
CREATE EXTERNAL TABLE hbase_table_1(key string, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = "colfam1:val")
TBLPROPERTIES("hbase.table.name" = "testtable");

Impala will fail to load the table with an error:

CAUSED BY: TableLoadingException: Failed to load metadata for HBase table:

hbase_hive_table_1
CAUSED BY: IndexOutOfBoundException: Index: 1, Size: 1

Impala should report a proper error instead. Also, Hive can query the table.