[
https://issues.redhat.com/browse/TEIID-5908?page=com.atlassian.jira.plugi...
]
Steven Hawkins commented on TEIID-5908:
---------------------------------------
For some reason we are receiving following error when running a query
on the table with this field in VDB.
That would appear to be a driver issue. This is similar to
https://issues.apache.org/jira/browse/KAFKA-5067 - which shows a very simple jdbc query
that results in the same exception. The pg driver does handle the case of using
getTimestamp with TIMESTAMP WITH TIMEZONE, but the redshift driver must not.
You can change the source type to string to confirm that you are getting the correct
values back. If so, we could pursue the fix of using getString if getTimestamp fails and
attempt to parse the value ourselves.
Issue with "timestamp with timezone" redshift data type
-------------------------------------------------------
Key: TEIID-5908
URL:
https://issues.redhat.com/browse/TEIID-5908
Project: Teiid
Issue Type: Bug
Reporter: Chandra Akkinepalli
Assignee: Steven Hawkins
Priority: Major
Our data source is redshift and we are using redshift translator in JDV.
The source table has a couple of fields with data type "timestamp with
timezone". This is field is mapped to Teiid source model with a data type timestamp.
For some reason we are receiving following error when running a query on the table with
this field in VDB.
*"SQL Error [30504] [50000]: TEIID30504 Remote
org.teiid.core.TeiidProcessingException: TEIID30504 SRC_RS_HYDRA: 22003 Unexpected
exception while translating results: [Amazon][JDBC](10140) Error converting value to
Timestamp"*
The fields which have source data type of "timestamp without timezone" mapped
to teiid data type of timestamp work just fine.
Please let me know if you have any questions.
Thanks,
Chandra
--
This message was sent by Atlassian Jira
(v7.13.8#713008)