[
https://issues.jboss.org/browse/TEIID-2175?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2175.
-----------------------------------
Resolution: Done
Added range checks for 8.0/8.1 clients and a system property (org.teiid.longDatesTimes)
that can be set to change their serialization version to 0 and avoid range exceptions.
Also changed the default date/time serialization to the 64-bit long version to avoid any
issues moving forward.
document and possibly provide a workaround for 32-bit dates
-----------------------------------------------------------
Key: TEIID-2175
URL:
https://issues.jboss.org/browse/TEIID-2175
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
To have a more compact format Teiid is using a 32-bit serialized date. This is
consistent with the jdbc spec as it allows for dates between 1900 and the end of 9999.
Years prior to and after that range are allowed in java, so we make it explicit that these
values may get truncated.
The workaround would be similar to the allow NAN property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira