Bug 1167321
| Summary: | Enable setting on MongoDB translator for controlling timezone setting for Date and Timestamp columns in some data sources | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Filip Elias <felias> | |
| Component: | Teiid | Assignee: | Van Halbert <vhalbert> | |
| Status: | CLOSED WONTFIX | QA Contact: | Filip Elias <felias> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.1.0 | CC: | atangrin, drieden, felias, kpalko, mbaluch, nshendye, vhalbert | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
For JDG, MongoDB and Solr data sources, it has been observed that Date and Timestamp columns in the resultset are affected by a time zone of JBoss Data Virtualization server. For these data sources, there is no remote notion of Calendar based time-stamp. The acceptable approach would be to have the respective translators updated with a server time zone setting (similar to JDBC) and have the translator adjust the UTC value to keep the calendar fields consistent. This way the server will always return the same values for Date and Timestamp columns even though the time zone of the server is changed.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1275333 1275335 (view as bug list) | Environment: | ||
| Last Closed: | 2016-01-27 14:09:55 UTC | Type: | Enhancement | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1275333 | |||
|
Description
Filip Elias
2014-11-24 13:12:47 UTC
The engineer considers this an enhancement and would like to target this to the 8.10 branch, which means it would be in DV 6.2. I have no problem to postpone this until DV 6.2. Moved to DV 6.3, as where TEIID 8.10 will be included. Steven Hawkins <shawkins> updated the status of jira TEIID-3231 to Resolved MongoDB values are in utc https://docs.mongodb.org/v3.0/reference/bson-types/#document-bson-type-timestamp so it's expected that their display will change if the Teiid server is in a different timezone. Steven Hawkins <shawkins> updated the status of jira TEIID-3231 to Closed all source dates are effectively UTC which means that it's expected that they will display differently if the teiid server timezone changes. |