[
https://issues.jboss.org/browse/TEIID-3938?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3938:
-------------------------------------
This issue sending round n round again with Olingo. There are lots of tests failing. They
wrote for consumption the GMT is assumed, but on production side there the timezone set on
the Time/Date/Timestamp is assumed. In cases of Edm.Date and Edm.TimeOfDay, I am going to
convert them to GMT based time object then output the string form of it.
EdmDate and EdmTimeOfDay output in local timezone
-------------------------------------------------
Key: TEIID-3938
URL:
https://issues.jboss.org/browse/TEIID-3938
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.12.5
EdmDate and EdmTimeOfDay both assume GMT for incoming string values - however when the
convert from Java objects to string they use the local/default Calendar. So when Teiid is
on a server not in GMT date and time value sent via the odata4 translator will likely be
wrong.
Ramesh:
I have posted a question to the Olingo development group here
http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.ap...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)