You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Abhishek Rawat (JIRA)" <ji...@apache.org> on 2019/04/24 17:00:00 UTC

[jira] [Updated] (IMPALA-1856) Missing datatypes from JDBC DBMD.getTypeInfo() call

     [ https://issues.apache.org/jira/browse/IMPALA-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhishek Rawat updated IMPALA-1856:
-----------------------------------
    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>*

  was:
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.


> Missing datatypes from JDBC DBMD.getTypeInfo() call
> ---------------------------------------------------
>
>                 Key: IMPALA-1856
>                 URL: https://issues.apache.org/jira/browse/IMPALA-1856
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 2.1
>         Environment: Impala 2.1 
> C5.3
> hive-jdbc 0.13
>            Reporter: Jonathan Seidman
>            Assignee: Abhishek Rawat
>            Priority: Minor
>              Labels: jdbc, odbc, ramp-up, supportability
>
> 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>*



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org