[IMPALA-167] Impala should gracefully handle unsupported Hive table types, specifically VIEWS

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 0.6
• Assignee: Lenni Kuff
• Reporter: Lenni Kuff
• Created: 23/Mar/13 14:54
• Updated: 24/Mar/13 17:03
• Resolved: 24/Mar/13 17:03

Description

If if we attempt to load the metadata for an unsupported Hive table type, such as a VIEW we get an error like below. Instead we should check the table type and throw a more intelligible error message if it is not a MANAGED or EXTERNAL table. This can be done in Table.load(...).

hive -e "create view test_view as select * from functional.alltypes limit 10"

impala-shell -i localhost -q "select * from test_view"
Caused by: com.cloudera.impala.catalog.Db$TableLoadingException: Failed to load metadata for table: test_view3
	at com.cloudera.impala.catalog.HdfsTable.load(HdfsTable.java:594)
	at com.cloudera.impala.catalog.Table.load(Table.java:111)
	at com.cloudera.impala.catalog.Db$LazyTableMap.loadTable(Db.java:227)
...
Caused by: java.lang.IllegalArgumentException: Can not create a Path from a null string
	at org.apache.hadoop.fs.Path.checkPathArg(Path.java:87)
	at org.apache.hadoop.fs.Path.<init>(Path.java:99)
	at com.cloudera.impala.catalog.HdfsTable.addPartition(HdfsTable.java:535)
	at com.cloudera.impala.catalog.HdfsTable.loadPartitions(HdfsTable.java:496)
	at com.cloudera.impala.catalog.HdfsTable.load(HdfsTable.java:590)