January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3924) Round should be marked as supported for Oracle

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3924?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3924. ----------------------------------- Resolution: Done Added into the function supports. This should be considered for 8.12.x as well. > Round should be marked as supported for Oracle > ---------------------------------------------- > > Key: TEIID-3924 > URL: https://issues.jboss.org/browse/TEIID-3924 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13 > > > The round function is not marked as supported, but should be as there has been support in oracle back to version 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3924) Round should be marked as supported for Oracle

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3924: ------------------------------------- Summary: Round should be marked as supported for Oracle Key: TEIID-3924 URL: https://issues.jboss.org/browse/TEIID-3924 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.13 The round function is not marked as supported, but should be as there has been support in oracle back to version 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 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 another issue. The fix did address the test case, but has introduced a problem with the integration tests: 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 Can you see if you are also getting this? > 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)

8 years, 11 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: --------------------------------------- > But if you want pass "%25" then you need to do pass "%2525" in that case? I'm saying that other logic paths such as the UriValidator pass unencoded values from the uri into the fromUriLiteral - which will then fail the decode call. You'll have to check with the odata folks on whether they intended the to/from uri value methods to handle encoding - it may be simpler just to have that logic in EntityResponse.buildLocation for now. > 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3519) Produce a wildfly kit

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3519?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3519. --------------------------------- Resolution: Done I generally consider this is done now. Will handle any issues individually. > Produce a wildfly kit > --------------------- > > Key: TEIID-3519 > URL: https://issues.jboss.org/browse/TEIID-3519 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.13 > > > Ahead of the 9 release it would be good to provide an option for an 8.x kit on wildfly. See also http://teiid.blogspot.com/2015/06/teiid-811-beta3-posted.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 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: ------------------------------------- But if you want pass "%25" then you need to do pass "%2525" in that case? > 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)

8 years, 11 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3920?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3920. --------------------------------- Fix Version/s: (was: 8.13) Resolution: Duplicate Issue > 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 > > 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)

8 years, 11 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3920?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3920: -------------------------------- Comment: was deleted (was: After looking at the source though, I'm not so sure about this. EdmDate and EdmTimeOfDay both assume GMT for incoming string values - however when the convert from Java objects to string they use the local/default Calendar. This seems like it could be a bug since it is asymmetric behavior. I can't find any spec reference on this either.) > 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3923) Remove databasetimezone property from odata4 translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3923?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-3923 at 1/22/16 10:11 AM: --------------------------------------------------------------- Steve: After looking at the source though, I'm not so sure about this. EdmDate and EdmTimeOfDay both assume GMT for incoming string values - however when the convert from Java objects to string they use the local/default Calendar. This seems like it could be a bug since it is asymmetric behavior. I can't find any spec reference on this either. Van: I agree, this is a good candidate for 8.12.x. Ramesh: I have posted a question to the Olingo development group here http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.ap... was (Author: rareddy): Steve: After looking at the source though, I'm not so sure about this. EdmDate and EdmTimeOfDay both assume GMT for incoming string values - however when the convert from Java objects to string they use the local/default Calendar. This seems like it could be a bug since it is asymmetric behavior. I can't find any spec reference on this either. Ramesh: I have posted a question to the Olingo development group here http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.ap... > Remove databasetimezone property from odata4 translator > ------------------------------------------------------- > > Key: TEIID-3923 > URL: https://issues.jboss.org/browse/TEIID-3923 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13 > > > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3920?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3920: -------------------------------- Comment: was deleted (was: I agree, this is a good candidate for 8.12.x. ) > 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)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016