[HIVE-12184] DESCRIBE of fully qualified table fails when db and table name match and non-default database is in use

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.1
• Fix Version/s: 2.0.0
• Component/s: SQL
• Hadoop Flags: Incompatible change
• Release Note: Document the incompatible change.
• Assignee: Naveen Gangam
• Reporter: Lenni Kuff
• Created: 15/Oct/15 06:20
• Updated: 16/Feb/16 23:51
• Resolved: 01/Dec/15 05:38

Description

DESCRIBE of fully qualified table fails when db and table name match and non-default database is in use.

Repro:

: jdbc:hive2://localhost:10000/default> create database foo;
No rows affected (0.116 seconds)
0: jdbc:hive2://localhost:10000/default> create table foo.foo(i int);

0: jdbc:hive2://localhost:10000/default> describe foo.foo;
+-----------+------------+----------+--+
| col_name  | data_type  | comment  |
+-----------+------------+----------+--+
| i         | int        |          |
+-----------+------------+----------+--+
1 row selected (0.049 seconds)

0: jdbc:hive2://localhost:10000/default> use foo;

0: jdbc:hive2://localhost:10000/default> describe foo.foo;
Error: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. Error in getting fields from serde.Invalid Field foo (state=08S01,code=1)

Issue Links

• is duplicated by: HIVE-11241 Database prefix does not work properly if table has same name
• is duplicated by: HIVE-11261 DESCRIBE database qualifier does not work when calling DESCRIBE on column or nested columns.