[teiid-issues] [JBoss JIRA] (TEIID-2671) Hive Metadata load incorrectly resolves data types

[Ramesh Reddy (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-2671.
---------------------------------

    Resolution: Done


1) Hive 0.11 driver can return the types names with spaces appended to it, to trimming them before the checking for defined type is required to detect correct runtime type
2) 0.71 driver when originally the translator developed it looks like in resultset.getTimestamp(index, cal) method cal parameter is ignored, and in 0.11 this method is written as not supported
3) correction for above was required to retrive the timestamp value correctly
4) Since we are recommending 0.11, updated the module.xml with correct version numbers in the documents section
5) Hive also released Hive2 driver where the driver class is org.apache.hive.jdbc.HiveDriver, provided ds example for this driver in docs section
6) tested with both drivers against the local and gss database
                
> Hive Metadata load incorrectly resolves data types
> --------------------------------------------------
>
>                 Key: TEIID-2671
>                 URL: https://issues.jboss.org/browse/TEIID-2671
>             Project: Teiid
>          Issue Type: Bug
>    Affects Versions: 8.4
>            Reporter: Filip Nguyen
>            Assignee: Ramesh Reddy
>            Priority: Blocker
>             Fix For: 8.4.1, 8.6
>
>
> The metadata load uses DESCRIBE keyword which tires to retrieve type name in String runtimeType = getRuntimeType(type);
> However, with Hive 0.11 the type name is returned with padding spaces. Hence all the data types are resolved to default java.lang.String for Hive Translator.
> This relates to 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira