[teiid-issues] [JBoss JIRA] (TEIID-3914) Datetime values not properly encoded in OData4 entity identifiers

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151219#comment-13151219 ] 

Ramesh Reddy commented on TEIID-3914:
-------------------------------------

What I meant was to somehow have Olingo clone version in our build, or way to override the behavior in our code base, such that we can mitigate the issue until we upgrade Olingo versions in between.  

> 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: Steven Hawkins
>              Labels: odata,
>
> 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)