September 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2228) Add ODBC support for pg_client_encoding()

by Van Halbert (JIRA)

Van Halbert created TEIID-2228: ---------------------------------- Summary: Add ODBC support for pg_client_encoding() Key: TEIID-2228 URL: https://issues.jboss.org/browse/TEIID-2228 Project: Teiid Issue Type: Enhancement Components: ODBC Affects Versions: 7.4.4 Reporter: Van Halbert Assignee: Steven Hawkins Provide support for pg_client_encoding() when using the ODBC driver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
7
0 / 0

[JBoss JIRA] (TEIID-2172) Load balancing configuration can result in extraneous "invalid session" messages

by Marc Shirley (JIRA)

Marc Shirley created TEIID-2172: ----------------------------------- Summary: Load balancing configuration can result in extraneous "invalid session" messages Key: TEIID-2172 URL: https://issues.jboss.org/browse/TEIID-2172 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.4.4 Environment: Clustered environment with load balancing enabled for the Teiid data source Reporter: Marc Shirley Assignee: Steven Hawkins When set up in a load balancing configuration with "SET NEW INSTANCE" as the check valid connection SQL in the datasource definition, repeated messages indicating an invalid session are created, similar to: 2012-08-24 10:39:58,818 WARN [org.teiid.SECURITY] (New I/O server worker #1-3) Processing exception 'The specified session ID "5Wt/6zzmsLy2" is invalid. It cannot be found in the userbase.' for session R8ZxYqjZzf/S. Exception type org.teiid.client.security.InvalidSessionException thrown from org.teiid.services.SessionServiceImpl.getSessionInfo(SessionServiceImpl.java:315). Enable more detailed logging to see the entire stacktrace. Not sure if this would be a defect in regards to the conditions that are resulting in the messages to be generated (ie, the old session id shouldn't be being reused), or an enhancement to clarify or adjust the log message or priority to indicate whether this will actually affect the query being submitted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
16
0 / 0

[JBoss JIRA] (TEIID-2225) ResultSet.isLast() blocks in non-continuous query mode

by Mark Addleman (JIRA)

Mark Addleman created TEIID-2225: ------------------------------------ Summary: ResultSet.isLast() blocks in non-continuous query mode Key: TEIID-2225 URL: https://issues.jboss.org/browse/TEIID-2225 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.1 Reporter: Mark Addleman Assignee: Steven Hawkins I am executing a query using submitExecute(StatementCallback) under non-continuous mode. In the onRow() method of the callback, I execute ResultSet.isLast(). The query is against an execution whose next() method initially throws DataNotAvailable.NO_POLLING. Some time later, it calls ExecutionContext.dataAvailable(). After 255 rows reported through the callback's onRow(), ResultSet.isLast() hangs. I know that the entire result set is ultimately returned from the execution's next() and it returns null at the last call. See https://community.jboss.org/thread/205559?tstart=0 for more detail -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
4
0 / 0

[JBoss JIRA] (TEIID-1992) Create Connector/Translator to support Infinispan as a data source

by Van Halbert (JIRA)

Van Halbert created TEIID-1992: ---------------------------------- Summary: Create Connector/Translator to support Infinispan as a data source Key: TEIID-1992 URL: https://issues.jboss.org/browse/TEIID-1992 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: Van Halbert Assignee: Van Halbert Create a Connector/Translator in order for Teiid to support Infinispan as a read-only data source on its initial release. Read Only because if someone is building an object cache, the primary means for updating the cache would not be thru relational means. However, if someone is wanting to add an object cache as a disparate data source for data integration for exposing the content, then this connector/translator will enable that. A goal here is to build an object translator framework that can easily plug in other object cache sources. Example, add support for Coherence. There was a Coherence connector/translator already created in the sandbox, for which, it will provide direction for the object translator. -- 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

11 years, 5 months

5
18
0 / 0

[JBoss JIRA] (TEIID-2219) NullPointer Exception when doing count aggregations on two individual columns from separate databases

by Ivan Chan (JIRA)

Ivan Chan created TEIID-2219: -------------------------------- Summary: NullPointer Exception when doing count aggregations on two individual columns from separate databases Key: TEIID-2219 URL: https://issues.jboss.org/browse/TEIID-2219 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.1 Environment: Running embedded mode Reporter: Ivan Chan Assignee: Steven Hawkins I have issues doing Count aggregations in 2 different databases. 2 out of 3 following cases fail... (But distinct count seems ok) <----------- CASE 1 ----------> SUM first, then COUNT => OK SUM(DB_2.field_1), COUNT(DB_1.field_1) select sum("FoodmartDataSourceJNDI_public_expense_fact"."amount") as "FoodmartDataSourceJNDI_public_expense_fact_amount_Sum", count("FoodmartDataSource_public_employee"."full_name") as "FoodmartDataSource_public_employee_full_name_Count" from "FoodmartDataSource_public"."employee" "FoodmartDataSource_public_employee" inner join "FoodmartDataSourceJNDI_public"."expense_fact" "FoodmartDataSourceJNDI_public_expense_fact" on ("FoodmartDataSource_public_employee"."store_id" = "FoodmartDataSourceJNDI_public_expense_fact"."store_id") SELECT g_0."store_id" AS c_0, g_0."full_name" AS c_1 FROM "public"."employee" AS g_0 ORDER BY c_0 SELECT g_0."store_id" AS c_0, SUM(g_0."amount") AS c_1 FROM "public"."expense_fact" AS g_0 GROUP BY g_0."store_id" ORDER BY c_0 <-----------CASE 2 ---------------> COUNT first, then SUM => ERROR COUNT(DB_1.field_1), SUM(DB_2.field_1) select count("FoodmartDataSourceJNDI_public_expense_fact"."category_id") as "FoodmartDataSourceJNDI_public_expense_fact_category_id_Count", sum("FoodmartDataSource_public_employee"."salary") as "FoodmartDataSource_public_employee_salary_Sum" from "FoodmartDataSource_public"."employee" "FoodmartDataSource_public_employee" inner join "FoodmartDataSourceJNDI_public"."expense_fact" "FoodmartDataSourceJNDI_public_expense_fact" on ("FoodmartDataSource_public_employee"."store_id" = "FoodmartDataSourceJNDI_public_expense_fact"."store_id") Caused by: java.lang.NullPointerException at org.teiid.query.processor.relational.GroupingNode.initialize(GroupingNode.java:184) at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:108) at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:113) at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:103) at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:194) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:130) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:109) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291) ... 123 more <-----------CASE 3 ---------------> COUNT on DB1.COL1 and COUNT on DB2.COL2 => ERROR COUNT(DB_1.field_1), COUNT(DB_2.field_1) select count("FoodmartDataSourceJNDI_public_expense_fact"."category_id") as "FoodmartDataSourceJNDI_public_expense_fact_category_id_Count", count("FoodmartDataSource_public_employee"."first_name") as "FoodmartDataSource_public_employee_first_name_Count" from "FoodmartDataSource_public"."employee" "FoodmartDataSource_public_employee" inner join "FoodmartDataSourceJNDI_public"."expense_fact" "FoodmartDataSourceJNDI_public_expense_fact" on ("FoodmartDataSource_public_employee"."store_id" = "FoodmartDataSourceJNDI_public_expense_fact"."store_id") Caused by: java.lang.NullPointerException at org.teiid.query.processor.relational.GroupingNode.initialize(GroupingNode.java:184) at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:108) at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:113) at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:103) at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:194) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:130) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:109) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291) ... 123 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
12
0 / 0

[JBoss JIRA] (TEIID-2193) System Catalog queries producing IllegalArgumentException: Invalid Type

by Warren Gibson (JIRA)

Warren Gibson created TEIID-2193: ------------------------------------ Summary: System Catalog queries producing IllegalArgumentException: Invalid Type Key: TEIID-2193 URL: https://issues.jboss.org/browse/TEIID-2193 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.1 Environment: Teiid 8.1 with AS 7.1.1 Reporter: Warren Gibson Assignee: Steven Hawkins All System Catalog queries producing IllegalArgumentException: Invalid Type Example queries: select * from SYS.VirtualDatabases select VDBName, SchemaName, Name, Type, NameInSource, IsPhysical, SupportsUpdates, UID, Cardinality, Description, IsSystem, IsMaterialized from SYS.Tables 09:50:55,300 DEBUG [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue12) Request Thread FwKHlqK21Snf.6 - error occurred: java.lang.IllegalArgumentException: Invalid type: org.teiid.metadata.Schema. at org.teiid.query.metadata.TransformationMetadata.createInvalidRecordTypeException(TransformationMetadata.java:619) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.metadata.TransformationMetadata.getModelID(TransformationMetadata.java:253) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.metadata.TempMetadataAdapter.getModelID(TempMetadataAdapter.java:175) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.metadata.TempMetadataAdapter.getModelID(TempMetadataAdapter.java:175) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.plantree.PlanNode.recordDebugAnnotation(PlanNode.java:423) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.rules.RulePushLimit.raiseAccessOverLimit(RulePushLimit.java:235) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.rules.RuleRaiseAccess.raiseAccessNode(RuleRaiseAccess.java:293) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.rules.RuleRaiseAccess.execute(RuleRaiseAccess.java:76) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:457) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:199) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:188) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:433) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.Request.processRequest(Request.java:453) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:532) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:280) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:219) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:249) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
5
0 / 0

[JBoss JIRA] (TEIID-2191) Detect recursive view definitions

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2191: ------------------------------------- Summary: Detect recursive view definitions Key: TEIID-2191 URL: https://issues.jboss.org/browse/TEIID-2191 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 A feature from designer that was never added to the runtime is detection of recursive view definitions. Currently if a recursive view is supplied via ddl or translator it will cause a stackoverflow in the relational planner when it is accessed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
3
0 / 0

[JBoss JIRA] (TEIID-2196) The clearCache method (adminShell) which accepts the VDB name should verify the VDB name and report if not found

by Paul Nittel (JIRA)

Paul Nittel created TEIID-2196: ---------------------------------- Summary: The clearCache method (adminShell) which accepts the VDB name should verify the VDB name and report if not found Key: TEIID-2196 URL: https://issues.jboss.org/browse/TEIID-2196 Project: Teiid Issue Type: Enhancement Components: AdminApi Affects Versions: 7.7.1 Reporter: Paul Nittel Assignee: Steven Hawkins Priority: Minor Fix For: 8.2 The clearCache(type, vdb, vdb-version) should report when the VDB and version specified does not exist. Presently (version 7.7.1/EDS 5.3) it appears to have been successful, even if the VDB name specified is a wildcard character. As an example, no exception was thrown for this: clearCache("PREPARED_PLAN_CACHE","*",1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
5
0 / 0

[JBoss JIRA] (TEIID-2227) Add support for a return statement

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2227: ------------------------------------- Summary: Add support for a return statement Key: TEIID-2227 URL: https://issues.jboss.org/browse/TEIID-2227 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins In many situations it would be convenient to have a return statement in the procedure language. It could optionally support a return value for procedures returning scalar values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1725) ResultSet metadata error with JDBC handled statements

by Steven Hawkins (JIRA)

ResultSet metadata error with JDBC handled statements ----------------------------------------------------- Key: TEIID-1725 URL: https://issues.jboss.org/browse/TEIID-1725 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Using a preparedstatement of SET / SHOW / transaction statements will fail if resultset metadata is requested prior to execution. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2012