[
https://issues.jboss.org/browse/TEIID-3920?page=com.atlassian.jira.plugin...
]
Ramesh Reddy updated TEIID-3920:
--------------------------------
Comment: was deleted
(was: After looking at the source though, I'm not so sure about this. 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. This seems like it could be a
bug since it is asymmetric behavior. I can't find any spec reference on this
either.)
Datetime values not properly encoded in OData4 entity identifiers
-----------------------------------------------------------------
Key: TEIID-3920
URL:
https://issues.jboss.org/browse/TEIID-3920
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.13
When the primary key of an OData entry consists of a timestamp or datetime value an odata
get request returns the following error message:
java.net.URISyntaxException: Illegal character in scheme name at index n:
tablename(partofkey='keyvalue',datepartofkey=2016-01-13 11:25:03.884)
For more information visit this thread on the user forums in which Steven Hawkins said:
"Actually there is an issue with our handling of building the entity id to go into
the response. We are not properly encoding datatime values.''
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)