April 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1980) JDBC connection QueryTimeout property appears to be ignored

by Paul Nittel (JIRA)

Paul Nittel created TEIID-1980: ---------------------------------- Summary: JDBC connection QueryTimeout property appears to be ignored Key: TEIID-1980 URL: https://issues.jboss.org/browse/TEIID-1980 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Paul Nittel Assignee: Steven Hawkins While testing an EDS patch, I tried to constrain a query by adding ;QueryTimeout=1 to my JDBC connection string. This had no apparent effect. (The query--a repeated UNION ALL of huge tables, followed by a descending ORDER BY--takes over 30 seconds.) I also tried 3 and 10 second timeouts, but all allowed the query to continue to completion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
11
0 / 0

[JBoss JIRA] (TEIID-2008) Allow client max object size to be settable

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2008: ------------------------------------- Summary: Allow client max object size to be settable Key: TEIID-2008 URL: https://issues.jboss.org/browse/TEIID-2008 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 The default 32 MB for max object size may be too small in custom scenarios or when there are numerous warnings attached to results. This should be a settable property via the client settings properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] (TEIID-2001) Skip loading of Function/Other models during the Index Based VDBs

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2001: ----------------------------------- Summary: Skip loading of Function/Other models during the Index Based VDBs Key: TEIID-2001 URL: https://issues.jboss.org/browse/TEIID-2001 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 Teiid only can read metadata from the PHYSICAL and VIRTUAL models, the OTHER (XSD) or FUNCTION models are there to represent the vdb structure but no metadata is actually loaded. FUNCTION model is still being loaded as original at the parse time. Lack of metadata is being flagged as an error during load, this needs to be fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] (TEIID-1989) Interval counter

by Mark Addleman (JIRA)

Mark Addleman created TEIID-1989: ------------------------------------ Summary: Interval counter Key: TEIID-1989 URL: https://issues.jboss.org/browse/TEIID-1989 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins In order to coordinate reusable executions across time windows, the CommandContext should include a counter of the number of intervals that have been executed. An interval is defined as all participating executions returning null. For more details, see https://community.jboss.org/thread/197562?start=0&tstart=0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] (TEIID-1998) Deployed translator JAR fails to be loaded when used in the VDB

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1998: ----------------------------------- Summary: Deployed translator JAR fails to be loaded when used in the VDB Key: TEIID-1998 URL: https://issues.jboss.org/browse/TEIID-1998 Project: Teiid Issue Type: Bug Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 Caused by: org.jboss.modules.ModuleNotFoundException: Module async-translator.jar:main is not found in local module loader @6cd24e3f (roots: /home/rareddy/testing/jboss-as-7.1.1.Final/modules) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204) at org.teiid.jboss.VDBService.getExecutionFactory(VDBService.java:260) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] (TEIID-2012) Errors in Column Name Validation

by Ted Jones (JIRA)

Ted Jones created TEIID-2012: -------------------------------- Summary: Errors in Column Name Validation Key: TEIID-2012 URL: https://issues.jboss.org/browse/TEIID-2012 Project: Teiid Issue Type: Bug Affects Versions: 7.7 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 7.7.1 When generating columns names in Designer with ":" in them, a parse error is thrown in the transformation. Also, using the keyword "value" in a transformation for a column name errors until "" are added to it. The "" should be added by the Teiid validator. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
9
0 / 0

[JBoss JIRA] (TEIID-1986) Exception on the slave node during materialization table load

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1986: ----------------------------------- Summary: Exception on the slave node during materialization table load Key: TEIID-1986 URL: https://issues.jboss.org/browse/TEIID-1986 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 8.0 I am consistently seeing the below exception, when the slave node trying to refresh the cache. After the failed attempt the cache seems to be getting TTL refreshed, so it keeps serving the old results until the cache time expires again. Next time it loads fine. er:server-slave] 16:40:01,677 ERROR [org.teiid.PROCESSOR.MATVIEWS] (Worker1_QueryProcessorQueue11) TEIID30015 Failed to load materialized view table #MAT_PARTSVIRTUAL.SUPPLIERINFO.: [TeiidProcessingException] TEIID30495: Error Code:TEIID30495 Message:TEIID30495 The request lqd0bkjp5nY2.5 has been closed. [Server:server-slave] at org.teiid.dqp.internal.process.DQPCore.getRequestWorkItem(DQPCore.java:503) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:179) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:125) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:365) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:154) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:140) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:167) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:196) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:128) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:107) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.processor.BatchCollector$BatchProducerTupleSource.nextTuple(BatchCollector.java:86) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.tempdata.TempTable$UpdateProcessor.process(TempTable.java:227) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.tempdata.TempTable$InsertUpdateProcessor.process(TempTable.java:89) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.tempdata.TempTable.insert(TempTable.java:582) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.tempdata.TempTableDataManager.loadGlobalTable(TempTableDataManager.java:449) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.tempdata.TempTableDataManager.access$0(TempTableDataManager.java:432) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.tempdata.TempTableDataManager$2.call(TempTableDataManager.java:425) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.query.tempdata.TempTableDataManager$2.call(TempTableDataManager.java:1) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_26] [Server:server-slave] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_26] [Server:server-slave] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:239) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) [teiid-engine-8.0.0.Beta2.jar:8.0.0.Beta2] [Server:server-slave] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] [Server:server-slave] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] [Server:server-slave] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
7
0 / 0

[JBoss JIRA] (TEIID-1995) Misleading error message

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1995: ------------------------------------- Summary: Misleading error message Key: TEIID-1995 URL: https://issues.jboss.org/browse/TEIID-1995 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.7.1 Newer vms validate Date/Time values as part of the parsing routine, however our logic only expects the parse to fail if there is an invalid format. Thus the error message may be misleading on newer vms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[JBoss JIRA] (TEIID-1965) Ingres10 as a Teiid Source - correlated subquery failing with Error Code 2118 Message:'Invalid qualifier

by Warren Gibson (JIRA)

Warren Gibson created TEIID-1965: ------------------------------------ Summary: Ingres10 as a Teiid Source - correlated subquery failing with Error Code 2118 Message:'Invalid qualifier Key: TEIID-1965 URL: https://issues.jboss.org/browse/TEIID-1965 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Reporter: Warren Gibson Assignee: Steven Hawkins The following query is failing in BQT testing: SELECT TIMEVALUE, BYTENUM, (SELECT B.FLOATNUM FROM BQT1.SMALLA AS B WHERE (B.INTKEY = (SELECT A.INTKEY FROM BQT1.SMALLA AS A WHERE (A.STRINGNUM > 10) AND (A.INTKEY = B.INTKEY))) AND (B.INTKEY = A.INTKEY)) FROM bqt1.smalla AS a Error Code:2118 Message:Remote org.teiid.core.TeiidProcessingException: Error Code:2118 Message:Source: Error Code:2118 Message:'Invalid qualifier 'g_1'. 'g_1' must be declared in the FROM clause or equivalent. If used in a target list, 'g_1' must be declared at the current scope.' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.timevalue, cast(g_0.bytenum AS tinyint), (SELECT g_1.floatnum FROM smalla AS g_1 WHERE g_1.intkey = g_0.intkey AND g_1.intkey = (SELECT g_2.intkey FROM smalla AS g_2 WHERE g_2.stringnum > '10' AND g_2.intkey = g_1.intkey)) FROM smalla AS g_0] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIID-1328) API request: Programatically modify the VDB

by Mark Addleman (JIRA)

API request: Programatically modify the VDB -------------------------------------------- Key: TEIID-1328 URL: https://jira.jboss.org/browse/TEIID-1328 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 7.1 Reporter: Mark Addleman Assignee: Steven Hawkins Priority: Minor I'd like an API to programatically modify the VDB. It would be ideal to modify the VDB using DDL through Teiid. Our primary use case is accessing a dynamic set of datasources through Teiid. When a datasource is added, we would INSERT the appropriate entries into MODEL, PROPERTIES, DATASOURCES tables. Teiid would reread the appropriate metadata from the associated translators. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

6
35
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2012