[
https://issues.jboss.org/browse/TEIID-2671?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2671:
---------------------------------------
If we are going to require .11, then yes we can remove the override. If not, the override
should stay and also apply to the column types. We can also look at adding auto-version
detection logic like the other jdbc translators so that the user doesn't have to
explicitly set to trim.
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