[teiid-issues] [JBoss JIRA] (TEIID-3938) EdmDate and EdmTimeOfDay output in local timezone

Ramesh Reddy (JIRA) issues at jboss.org
Mon Feb 1 19:18:00 EST 2016


    [ https://issues.jboss.org/browse/TEIID-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157361#comment-13157361 ] 

Ramesh Reddy commented on TEIID-3938:
-------------------------------------

EdmDateTimeOffset has Timezone information, but tests are written such that they expected "GMT", but there were series of conversions between default time zone and GMT to make all work. So, I simply removed the GMT for EdmdatTimeOffset and let the TZ set on the object take precedence. For unit tests I introduced system property, to convert back to GMT.

Where as Edm.Date and Edm.TimeOfDay do not have TZ info, so coming in I assumed they are "GMT", while going out converted the time to GMT and then sent it out.  So, I thought the flag is not required here.

> 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.apache.olingo.dev+page:1+mid:bfghfslrpwyjh6ii+state:results



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the teiid-issues mailing list