[teiid-issues] [JBoss JIRA] (TEIID-3920) Datetime values not properly encoded in OData4 entity identifiers
Ramesh Reddy (JIRA)
issues at jboss.org
Fri Jan 22 10:11:00 EST 2016
[ https://issues.jboss.org/browse/TEIID-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Reddy reassigned TEIID-3920:
-----------------------------------
Description:
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 Steven Hawkins 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.''
was:
The databasetimezone execution property is not used - and not needed since all date/time information needs to be in gmt or with an explicit timezone.
This is a candidate for 8.12.5 as well.
Summary: Datetime values not properly encoded in OData4 entity identifiers (was: Remove databasetimezone property from odata4 translator)
Assignee: Ramesh Reddy (was: Steven Hawkins)
This is duplicate of TEIID-3914, I accidentally used different commit tag while commiting the code to the github. To keep the code along with the JIRA I moved original to TEIID-3923, and going to mark this as duplicate of TEIID-3914
> Datetime values not properly encoded in OData4 entity identifiers
> -----------------------------------------------------------------
>
> Key: TEIID-3920
> URL: https://issues.jboss.org/browse/TEIID-3920
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.13
>
>
> 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 Steven Hawkins 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