[
https://issues.jboss.org/browse/TEIID-2671?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2671:
-------------------------------------
Sorry I confused myself
- Looking more closely TEIID-2524, was about column names, not column types, so that got
fixed in 0.11, so one may never need to define a "importer.trimColumNames"
importer property. Only working with 0.10 one may need this.
- This JIRA was talking about the data types on the same columns, but while testing I have
not seen the behavior indicated.
Filip, do have a sample data file/vdb that I can use to duplicate the issue?
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