[
https://issues.apache.org/jira/browse/IMPALA-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808987#comment-16808987
]
Tim Armstrong commented on IMPALA-1856:
---------------------------------------
This behaviour is covered by a test - FrontEndTest.TestGetTypeInfo() but the
test wasn't updated when new data types would added. It would be good if we
could somehow avoid this problem when adding new types so that if we add a new
type and forget to update GetTypeInfo(), the test fails.
We should also add an end-to-end test for the HS2 GetTypeInfo() RPC to
tests/hs2/test_hs2.py. There is a test gap here.
> 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
> 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]
