[
https://issues.jboss.org/browse/TEIID-4263?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-4263:
----------------------------------
Fix Version/s: 9.1
The intent of the check is to filter invalid timestamps that are allowed by the linent
Java parsing, such as 2011-09-07 24:00:00 or 2011-02-29 00:03:00. Unfortunately this
catches the transition times as well.
Workarounds include using the parseTimestamp function or having the server in a non-DST
timezone. And this will only be an issue on sources where the timestamp value is stored
as a string - if the database is using/returning a Timestamp this will not occur as
described with just a select *
StringToTimestamp in convert fails during DST transition hour
-------------------------------------------------------------
Key: TEIID-4263
URL:
https://issues.jboss.org/browse/TEIID-4263
Project: Teiid
Issue Type: Bug
Components: Common
Affects Versions: 8.7.7.6_2
Reporter: Guy Davis
Assignee: Steven Hawkins
Fix For: 9.1
Attachments: ArgentinaTest.java
Issue is due to
[
https://github.com/teiid/teiid/blob/master/common-core/src/main/java/org/...
| this line] in StringToTimestampTransform.java. In particular, if you pass in a string
date for a timestamp at the beginning of the DST transition hour, the result will be an
hour in the future or past, so this string comparison fails, throwing TEIID10060
exception.
Examples include:
* America/Edmonton 2016-03-13 02:00:00
* America/Argentina/Buenos_Aires 1991-10-20 00:00:00
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)