January 2016 - teiid-issues - Jboss List Archives

[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 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)

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: There is still another olingo issue needed on TimeOfDay and Date handling as well. Ramesh do you want me to log something for those?) > 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-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 to/from uri literal logic is called with different assumptions about uri encoding. If you change the test case to: {code} response = http.newRequest(baseURL + "/northwind/m/x(a='a%25''',b=2011-09-11T00:00:00Z)") {code} It will fail since it passes in 'a%'', rather than the encoded 'a%25'', to the from uri method. > 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-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 commented on TEIID-3923: ------------------------------------- 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) Remove databasetimezone property from odata4 translator

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 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-3920 > URL: https://issues.jboss.org/browse/TEIID-3920 > 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-3923) Remove databasetimezone property from odata4 translator

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3923: ----------------------------------- Summary: 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-3921) Accumulo translator doesn't end query execution when there are no tablet servers

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3921?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3921: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Accumulo translator doesn't end query execution when there are no tablet servers > -------------------------------------------------------------------------------- > > Key: TEIID-3921 > URL: https://issues.jboss.org/browse/TEIID-3921 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.3 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > > Teiid accumulo translator doesn't interrupt query execution when the accumulo instance is not running. > There might be a situation that Zookeeper instance is running, but Accumulo is not. > The translator, even though there is no tablet server entry in zookeeper, for given accumulo instance, executes the query. The query is running until query timeout exceeds. There is no indication of the fact, that accumulo tablet server is not present/responding except for > {code} > 09:25:46,539 WARN [org.apache.accumulo.core.client.impl.ServerClient] (Worker3_QueryProcessorQueue21) There are no tablet servers: check that zookeeper and accumulo are running. > {code} > There might be even situation, that Accumulo stopped in unusual way and didn't alter the tablet server information in Zookeeper, this way, there is a tablet server entry present in Zookeeper, but the tablet server is in fact not running. So Teiid should check the tablet server's address which received from Zookeeper. > Interesting to note is the fact, that the same problem can be examined in accumulo's shell: > {code} > $ bin/accumulo shell -u root > Password: ****** > 2016-01-22 10:02:05,604 [impl.ServerClient] WARN : There are no tablet servers: check that zookeeper and accumulo are running. > {code} > and then the shell hangs. Teiid needs to overcome this limitation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3920?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3920: ------------------------------------- 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-3920 > URL: https://issues.jboss.org/browse/TEIID-3920 > 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-3921) Accumulo translator doesn't end query execution when there are no tablet servers

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3921?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3921: ------------------------------------- Ideally IMO that needs to go into any extension that is there to check the validity of the connection in JCA interface. > Accumulo translator doesn't end query execution when there are no tablet servers > -------------------------------------------------------------------------------- > > Key: TEIID-3921 > URL: https://issues.jboss.org/browse/TEIID-3921 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.3 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > Teiid accumulo translator doesn't interrupt query execution when the accumulo instance is not running. > There might be a situation that Zookeeper instance is running, but Accumulo is not. > The translator, even though there is no tablet server entry in zookeeper, for given accumulo instance, executes the query. The query is running until query timeout exceeds. There is no indication of the fact, that accumulo tablet server is not present/responding except for > {code} > 09:25:46,539 WARN [org.apache.accumulo.core.client.impl.ServerClient] (Worker3_QueryProcessorQueue21) There are no tablet servers: check that zookeeper and accumulo are running. > {code} > There might be even situation, that Accumulo stopped in unusual way and didn't alter the tablet server information in Zookeeper, this way, there is a tablet server entry present in Zookeeper, but the tablet server is in fact not running. So Teiid should check the tablet server's address which received from Zookeeper. > Interesting to note is the fact, that the same problem can be examined in accumulo's shell: > {code} > $ bin/accumulo shell -u root > Password: ****** > 2016-01-22 10:02:05,604 [impl.ServerClient] WARN : There are no tablet servers: check that zookeeper and accumulo are running. > {code} > and then the shell hangs. Teiid needs to overcome this limitation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

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

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: Resolved upstream * https://issues.apache.org/jira/browse/OLINGO-854 * https://issues.apache.org/jira/browse/OLINGO-853 Need to override the local version with those modifications. Also, I will be moving to Olingo 4.1.0 to be closer to Olingo project's current version) > Remove databasetimezone property from odata4 translator > ------------------------------------------------------- > > Key: TEIID-3920 > URL: https://issues.jboss.org/browse/TEIID-3920 > 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016