[
https://issues.apache.org/jira/browse/IMPALA-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824625#comment-16824625
]
Abhishek Rawat commented on IMPALA-1856:
----------------------------------------
The Impala JDBC driver returns following types from
DatabaseMetadat.getTypeInfo():
TINYINT
BIGINT
CHAR
DECIMAL
INT
SMALLINT
FLOAT
REAL
DOUBLE
ARRAY
MAP
STRING
STRUCT
VARCHAR
BOOLEAN
TIMESTAMP
It seems the driver no longer calls Impala for getting the supported types info
and has its own internal logic to figure out what types are supported.
> 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
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
