[teiid-issues] [JBoss JIRA] (TEIID-3914) Datetime values not properly encoded in OData4 entity identifiers
Ramesh Reddy (JIRA)
issues at jboss.org
Fri Jan 22 12:31:00 EST 2016
[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152644#comment-13152644 ]
Ramesh Reddy commented on TEIID-3914:
-------------------------------------
I am looking at at their latest code, they changed parser code and removed antlr dependency, I should have realized you are looking at the current version. But even there I did not see before but they are decoding the whole path at the beginning, so there is no reason for them to be using the "fromUriLiteral" in that case.. arrrg. I will revert the changes.
> 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)
More information about the teiid-issues
mailing list