[IMPALA-1856] MetadataOp.getTypeInfo() does not return all supported types

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Resolved
• Affects Version/s: Impala 2.1
• Fix Version/s: Impala 3.3.0
• Component/s: Frontend
• Labels: jdbc odbc ramp-up supportability
• Environment: Impala 2.1 ; C5.3; hive-jdbc 0.13
• Target Version: Impala 2.9.0
• Assignee: Abhishek Rawat
• Reporter: Jonathan Seidman
• Created: 06/Mar/15 21:40
• Updated: 25/Apr/19 02:43
• Resolved: 25/Apr/19 02:43

Description

The MetadataOp.getTypeInfo() does not return all the supported types. It's missing all the complex types (ARRAY, MAP, and STRUCT)  added in CDH5.5. Several of the primitive data types such as CHAR, VARCHAR, DECIMAL are also not being returned. Also, the newly added DATE type is not being returned.

There is also a testing gap and ideally whenever a new type is added or support for a type is changed the MetadataOp.getTypeInfo() should return the correct result set representing the supported types.

The Impala JDBC client should in theory call MetadataOp.getTypeInfo() but that is not happening in the latest version of the code. This Jira will only ensure that on Impala side the MetadataOp.getTypeInfo() returns correct results.

 

<Old Description>

Missing datatypes from JDBC DBMD.getTypeInfo() call:

Filing this here since it seems to be an Impala defect as opposed to a driver defect based on observed behavior. The following is seen from DBMD.getTypeInfo() call against Hive:

VOID 
BOOLEAN 
TINYINT 
SMALLINT 
INT 
BIGINT 
FLOAT 
DOUBLE 
STRING 
CHAR 
VARCHAR 
DATE 
TIMESTAMP 
BINARY 
DECIMAL 
ARRAY 
MAP 
STRUCT 
UNIONTYPE 
USER_DEFINED

And against Impala (2.1):

NULL_TYPE 
BOOLEAN 
TINYINT 
SMALLINT 
INT 
BIGINT 
FLOAT 
DOUBLE 
TIMESTAMP 
STRING 
BINARY

Note the missing newer datatypes (e.g. decimal, varchar).

This is with the Hive 0.13 driver. Please let me know if there's something I'm missing and this should be filed against the driver.

</Old Description>