[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=13152656#comment-13152656 ] 

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

>11:01:29,560 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /odata4/Loopy.1/MarketData/$metadata: java.lang.LinkageError: >org/apache/olingo/server/core/responses/MetadataResponse

Ok, this means the in-place replacement of classes will not work, I have to find an alternate way to deliver as patch to Olingo modules then. This is what I was concerned about at the beginning. I will add as patch file to the Olingo module that includes the source java file that contains 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)