[
https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3914:
-------------------------------------
The real question is if the Olingo parser when it parses also decodes the parameters and
key-predicates or not, which seems like they are NOT decoding them during parsing, but
using the fromUriLiteral. see ParserHelper.parseFunctionParameters and
ParserHelper.parseKeyPredicate, but at the same time they are decoding the query options.
so, little confusing. The one thing working is they only used "fromUriLiteral"
for key-predicates. So, I will ask them
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)