]
Steven Hawkins resolved TEIID-5362.
-----------------------------------
Resolution: Incomplete Description
Marking as incomplete description. Based upon the description this does not appear
directly related to odata and seems instead to be an issue with the database driver.
Given that the user has an acceptable workaround, marking this as incomplete description.
Odata4 outputs in wrong timezone
--------------------------------
Key: TEIID-5362
URL:
https://issues.jboss.org/browse/TEIID-5362
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.12.13.6_4
Reporter: Debbie Steigner
Assignee: Steven Hawkins
The incoming odata4 request is requesting the records at 08:52Z (specifying UTC time).
The DataVirt server (running in US/Chicago time) converts that into SQL to ask the
database for records at 03:52 (with no timezone specifier... should be in local time, or
US/Chicago). The database should recognize that the 03:52 Local time should be converted
back to 08:52Z to match the DB records, however, it is not. This (and other tests), leads
us to the conclusion that the database session/connection is actually not using US/Chicago
(-5:00) timezone, but is instead using the UTC timezone. Unfortunately, we were not able
to confirm either in the logs or in the configuration, where the connection was being set
up in UTC timezone.
.