November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3831) For results set caching there should scope metadata for source tables/procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3831?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3831: --------------------------------------- The approach here will be to look for a DETERMINISM relational property on the schema / model properties and on the non-temporary tables / procedures in the source queries (We will already assume session scoping for temporary tables). We'll also allow the cache directive scope to influence the determinism level. I'll see if it makes sense to add a another way to set the scope programtically - it seems like we'll need that for TEIID-3738 > For results set caching there should scope metadata for source tables/procedures > -------------------------------------------------------------------------------- > > Key: TEIID-3831 > URL: https://issues.jboss.org/browse/TEIID-3831 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.x > > > Functions have optional metadata to convey their determinism, which affects the caching scope. However we don't have extension metadata or per execution metadata around source queries (there is a scope field on a cache directive, but that only applies to source level caching). We should provide a general mechanism so that users aren't required to manually override the result set cache scope. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3841) sap-nw-gateway translator wrongly encodes when a parameter includes a space

by Marc Shirley (JIRA)

Marc Shirley created TEIID-3841: ----------------------------------- Summary: sap-nw-gateway translator wrongly encodes when a parameter includes a space Key: TEIID-3841 URL: https://issues.jboss.org/browse/TEIID-3841 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Marc Shirley Assignee: Steven Hawkins Submitting a function through the sap-nw-gateway translator results in overzealous encoding of the URL when one of the parameters includes a space like "AA AB". The '?' character (along with the spaces in any parameters) in the expected URL [1] is encoded to '%3F' resulting in an error like [2] below. [1] https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/GetFl...'AA AB'&connectionid='0017' [2] org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 flightdemo: TEIID17013 Wrong response from source with HTTP Response Code 404: Vendor Code "005056A509B11EE1B9A8FEC11C21D78E": With message "Resource not found for the segment 'GetFlightDetails%3Fairlineid='AA%20AB'&connectionid='0017''.": Detail Error null -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3666. --------------------------------- Resolution: Done > VDB can deploy before datasource is bound > ----------------------------------------- > > Key: TEIID-3666 > URL: https://issues.jboss.org/browse/TEIID-3666 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.3 > Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.3, 8.7.2.6_2 > > > A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3586. --------------------------------- Resolution: Done > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12, 8.11.2, 8.7.2.6_2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3592. --------------------------------- Resolution: Done > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.2, 8.7.2.6_2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3838) Provide fail over capability to the data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3838?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3838. ----------------------------------- Resolution: Won't Fix As described this is already addressed by EAP. For the non-JDBC sources it is possible that this could be a feature, but we'd first want to ensure it wasn't already addressed by the connector or done in the JCA layer. > Provide fail over capability to the data source > ----------------------------------------------- > > Key: TEIID-3838 > URL: https://issues.jboss.org/browse/TEIID-3838 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > Provide fail over capability to the data source. > Here's what's being envisioned: > - similar to multi-source option, assign multiple data sources > - assign a specific order of reading > - only access 1 data source as part of a user query > - if the primary data source is down, go down the line in order, to the next available data source -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3840) teiid-outh-util.bat - typo in name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3840?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3840. ----------------------------------- Fix Version/s: 8.13 8.12.3 (was: 8.12.x) Resolution: Done The pull request was merged. Thanks Juraj. > teiid-outh-util.bat - typo in name > ---------------------------------- > > Key: TEIID-3840 > URL: https://issues.jboss.org/browse/TEIID-3840 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.10.1 > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Priority: Trivial > Fix For: 8.13, 8.12.3 > > > File name 'teiid-outh-util.bat' contains typo. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3805) HANA SUBSTRING function inconsistent with teiid behaviour

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3805?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3805: ------------------------------------------------ Debi Rieden <drieden(a)redhat.com> changed the Status of [bug 1278464|https://bugzilla.redhat.com/show_bug.cgi?id=1278464] from NEW to CLOSED > HANA SUBSTRING function inconsistent with teiid behaviour > --------------------------------------------------------- > > Key: TEIID-3805 > URL: https://issues.jboss.org/browse/TEIID-3805 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > When querying HANA using hana translator, there is an inconsistency in handling SUBSTRING with similar parameters: > {code:sql} > SELECT SUBSTRING('sth',20,1) FROM tablename > {code} > That is, when the starting offset supplied to SUBSTRING function is greater than the length of the string value, Teiid returns NULL in this case. > But when I run: > {code:sql} > SELECT SUBSTRING(STRINGNUM,20,1) FROM bqt1.smalla > {code} > (it is pushed to HANA and STRINGNUM column contains strings of length <=2) > I get empty strings instead of NULL values, which is default in Teiid. > This inconsistency is caused by different handling of such situation on HANA's side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3829) olingo module junit test failed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3829?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3829: ---------------------------------- Issue Type: Quality Risk (was: Bug) Fix Version/s: 8.12.3 Affects Version/s: 8.9 (was: 8.13) > olingo module junit test failed > ------------------------------- > > Key: TEIID-3829 > URL: https://issues.jboss.org/browse/TEIID-3829 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 8.9 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.3 > > > olingo module junit test failed: > {code} > Results : > Failed tests: > TestODataSQLBuilder.testEq:431->te:400->helpTest:227 expected:<...g0 WHERE g0.e1 = {t'[04]:20:02'} ORDER BY g0...> but was:<...g0 WHERE g0.e1 = {t'[16]:20:02'} ORDER BY g0...> > TestODataSQLBuilder.testTimeMethods:552->te:400->helpTest:227 expected:<...YEAR({ts'2008-10-13 [04]:20:02.0'}) = 2008 O...> but was:<...YEAR({ts'2008-10-13 [16]:20:02.0'}) = 2008 O...> > Tests run: 109, Failures: 2, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3829) olingo module junit test failed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3829?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3829. ----------------------------------- Resolution: Done Added a fixed timezone for the test setup. > olingo module junit test failed > ------------------------------- > > Key: TEIID-3829 > URL: https://issues.jboss.org/browse/TEIID-3829 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 8.9 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.3 > > > olingo module junit test failed: > {code} > Results : > Failed tests: > TestODataSQLBuilder.testEq:431->te:400->helpTest:227 expected:<...g0 WHERE g0.e1 = {t'[04]:20:02'} ORDER BY g0...> but was:<...g0 WHERE g0.e1 = {t'[16]:20:02'} ORDER BY g0...> > TestODataSQLBuilder.testTimeMethods:552->te:400->helpTest:227 expected:<...YEAR({ts'2008-10-13 [04]:20:02.0'}) = 2008 O...> but was:<...YEAR({ts'2008-10-13 [16]:20:02.0'}) = 2008 O...> > Tests run: 109, Failures: 2, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 November 2015