[teiid-issues] [JBoss JIRA] (TEIID-3914) Datetime values not properly encoded in OData4 entity identifiers
[
https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3914:
---------------------------------------
There is another issue. The to/from uri literal logic is called with different
assumptions about uri encoding. If you change the test case to:
{code}
response = http.newRequest(baseURL +
"/northwind/m/x(a='a%25''',b=2011-09-11T00:00:00Z)")
{code}
It will fail since it passes in 'a%'', rather than the encoded
'a%25'', to the from uri method.
Datetime values not properly encoded in OData4 entity identifiers
-----------------------------------------------------------------
Key: TEIID-3914
URL: https://issues.jboss.org/browse/TEIID-3914
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.12.4
Reporter: Simon Evenepoel
Assignee: Ramesh Reddy
Labels: odata,
Attachments: TEIID-3914.diff
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 [~shawkins] 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)