[
https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3914:
---------------------------------------
But if you want pass "%25" then you need to do pass
"%2525" in that case?
I'm saying that other logic paths such as the UriValidator pass unencoded values from
the uri into the fromUriLiteral - which will then fail the decode call. You'll have
to check with the odata folks on whether they intended the to/from uri value methods to
handle encoding - it may be simpler just to have that logic in
EntityResponse.buildLocation for now.
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)