January 2016 - teiid-issues - Jboss List Archives

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3914: ------------------------------------- I wrote that layer in the Olingo too, but I missed that one. I can correct it upstream, but I am thinking we may need another method to quickly update the Olingo bugs locally. > 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)

10 years, 2 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3914: --------------------------------------- See the buildLocation logic in https://github.com/apache/olingo-odata4/blob/master/lib/server-core-ext/s... or in our EntityCollectionResponse. For non-string values it is taking the java toString as the URI value. This is not correct for Timestamp, Binary, some Decimal values, etc. Even if we correct our handling in EntityCollectionResponse, we are then calling to EntityResponse to set the id again in the TeiidServiceHandler.createEntity method. Then beyond that, the response.writeCreatedEntity will again call EntityResponse.buildLocation (rather than reusing the id on the entity). > 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)

10 years, 2 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3914: ------------------------------------- What is the special character? The proper format for the time would be "yyyy-MM-dd'T'HH:mm:ss.SSS" > 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)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3912: --------------------------------------- I added the changes for this into Teiid 9. This fixed the aalto-xml module, created an olingo-common Teiid module with the common type code and the olingo common, aalto-xml, antlr, commons-lang wildfly modules. > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3915) OlingoBridge should be concurrent

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3915: ------------------------------------- Summary: OlingoBridge should be concurrent Key: TEIID-3915 URL: https://issues.jboss.org/browse/TEIID-3915 Project: Teiid Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.13, 8.12.5 The map in olingobridge needs to be safe for concurrent access. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3914: --------------------------------------- There is both a Teiid and an olingo issue here. The olingo EntityResponse logic for building the location and our code that was copied from there for EntityCollectionResponse do not account for types that have special uri string handling. Beyond that we need to set the id uri off of the base uri - as a releative uri it's still not valid. > 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)

10 years, 2 months

1
0
0 / 0

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

by Simon Evenepoel (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Simon Evenepoel updated TEIID-3914: ----------------------------------- 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 [~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.''_ was: When the primary key of an OData entry consists of a timestamp or datetime value an odata get request returns the following error message: For more information visit this thread on the user forums: [https://developer.jboss.org/message/949160] Steps to Reproduce: Make an OData V4 call to a table that has a timestamp or datetime value as part of the primary key. Labels: odata, (was: ) Forum Reference: https://developer.jboss.org/message/949160 > 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)

10 years, 2 months

1
0
0 / 0

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

by Simon Evenepoel (JIRA)

Simon Evenepoel created TEIID-3914: -------------------------------------- Summary: 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 When the primary key of an OData entry consists of a timestamp or datetime value an odata get request returns the following error message: For more information visit this thread on the user forums: [https://developer.jboss.org/message/949160] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3912: --------------------------------------- The aalto-xml module seems to be missing the module.xml file. Is this module needed? > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3912: --------------------------------------- Ok, I'll add a small common module with some other clean ups. > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016