May 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-998) Define a new schema based VDB deployer xml (previously defined by ConfigurationInfo.def)

by Ramesh Reddy (JIRA)

Define a new schema based VDB deployer xml (previously defined by ConfigurationInfo.def) ---------------------------------------------------------------------------------------- Key: TEIID-998 URL: https://jira.jboss.org/jira/browse/TEIID-998 Project: Teiid Issue Type: Sub-task Components: Common Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Attachments: vdb-deployer.xsd With the changes in the JCA branch the ConfigurationInfo.def file inside the VDB needs to be modified to accommodate the new connector definitions. Create a schema based XML file that can be used with both with Designer generated VDB and also for Dynamic VDB. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1051) Make the Connector (type) and RAR name be the same

by Ramesh Reddy (JIRA)

Make the Connector (type) and RAR name be the same -------------------------------------------------- Key: TEIID-1051 URL: https://jira.jboss.org/jira/browse/TEIID-1051 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Currently in the Admin API in 7.0 M3 getConnectorNames() call returns the Connectors that are available in the system. These are the Teiid Connector RAR files. However, ".RAR" extension is truncated for this call. When the a Connection Factory is created, it contains the "rar-name" as the full name with the extension. They both need to be same. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-834) CTC Testing -Queries should not depend on a Stored Procedure result set if the stored procedures is not designed to return a result set.

by Warren Gibson (JIRA)

CTC Testing -Queries should not depend on a Stored Procedure result set if the stored procedures is not designed to return a result set. ---------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-834 URL: https://jira.jboss.org/jira/browse/TEIID-834 Project: Teiid Issue Type: Bug Components: Integration Tests Environment: CTC Testing Reporter: Warren Gibson Assignee: Warren Gibson Fix For: 6.2.0 In prior releases the stored procedures result sets were returned in all cases. CTC stored procedure queries were written with the expectation of a result set being returned. That is no longer the case and result sets will only be returned when the stored procedure calls for a returned result set. CTC stored procedures queries need to be reviewed to eliminate their dependencies on result sets when the procedure is not designed to return a result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1014) PostgreSQL pushdown query SELECT COUNT(*) FROM BQT1.SmallA - producing NullPointerException

by Warren Gibson (JIRA)

PostgreSQL pushdown query SELECT COUNT(*) FROM BQT1.SmallA - producing NullPointerException --------------------------------------------------------------------------------------------- Key: TEIID-1014 URL: https://jira.jboss.org/jira/browse/TEIID-1014 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins Attachments: JavaNullPointer.txt SELECT COUNT(*) FROM xxxxxxxxxx is producing Java Null Pointer Exceptions in PostgreSQL pushdown. Log attached. Examples: SELECT COUNT(*) FROM BQT1.SmallA SELECT COUNT(*) FROM BQT1.MediumA SELECT COUNT(*) FROM BQT1.LargeA SELECT COUNT(*) FROM BQT2.SmallB SELECT COUNT(*) FROM BQT2.MediumB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1079) Provide deployer for the Translation Layer components.

by Ramesh Reddy (JIRA)

Provide deployer for the Translation Layer components. ------------------------------------------------------ Key: TEIID-1079 URL: https://jira.jboss.org/jira/browse/TEIID-1079 Project: Teiid Issue Type: Sub-task Components: Server Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 The translation layer properties will be provided to the teiid engine through "-tl.xml" properties. Teiid must provide a deployer to read this properties and create appropriate translation layer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-783) Fetch enhancements

by Steven Hawkins (JIRA)

Fetch enhancements ------------------ Key: TEIID-783 URL: https://jira.jboss.org/jira/browse/TEIID-783 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 6.2.0 Allow fetchsize to be set on resultsets and do not cache batches on the client when the cursor type is forward only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1076) When running BQT tests, an Assertion error is seen when batches are being processed

by Van Halbert (JIRA)

When running BQT tests, an Assertion error is seen when batches are being processed ----------------------------------------------------------------------------------- Key: TEIID-1076 URL: https://jira.jboss.org/jira/browse/TEIID-1076 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Van Halbert Assignee: Van Halbert Fix For: 7.0 I am testing BQT pushdown on MS3 and seeing several "java.lang.AssertionError" occurring on all sources. This is one example of a query and the exception. Any idea what is going on? SELECT BQT1.SmallA.StringKey, BQT1.SmallB.ByteNum FROM BQT1.SmallA, BQT1.SmallB WHERE BQT1.SmallA.StringKey = convert(BQT1.SmallB.ByteNum, string) AND BQT1.SmallA.IntKey >= 0 AND BQT1.SmallB.IntKey >= 0 ORDER BY BQT1.SmallA.StringKey 2010-04-28 08:17:11,027 ERROR [org.teiid.CONNECTOR] (WorkManager(2)-25_QueryProcessorQueue344368) Connector worker process failed for atomic-request=111.0.1.179477 java.lang.AssertionError: Assertion failed. at com.metamatrix.core.util.Assertion.failed(Assertion.java:76) at com.metamatrix.core.util.Assertion.assertTrue(Assertion.java:71) at com.metamatrix.core.util.Assertion.assertTrue(Assertion.java:63) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:284) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.more(ConnectorWorkItem.java:143) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:90) at com.metamatrix.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:136) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:260) at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:106) at com.metamatrix.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:147) at com.metamatrix.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:103) at com.metamatrix.query.processor.BatchCollector.collectTuples(BatchCollector.java:71) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:249) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:179) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:48) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:194) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:191) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:180) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:191) at org.teiid.dqp.internal.process.StatsCapturingWorkManager$WorkWrapper.run(StatsCapturingWorkManager.java:102) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 2010-04-28 08:17:11,027 WARN [org.teiid.PROCESSOR] (WorkManager(2)-25_QueryProcessorQueue344368) Processing exception 'java.lang.AssertionError: Assertion failed.' for request 111.0. Exception type com.metamatrix.api.exception.MetaMatrixProcessingException thrown from com.metamatrix.core.util.Assertion.failed(Assertion.java:76). Enable more detailed logging to see the entire stacktrace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1069) Admin API Data Source method are not needed

by Ramesh Reddy (JIRA)

Admin API Data Source method are not needed ------------------------------------------- Key: TEIID-1069 URL: https://jira.jboss.org/jira/browse/TEIID-1069 Project: Teiid Issue Type: Sub-task Components: AdminApi Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Based TEIID-1068, the addDataSource deleteDatasource getDatasourcePropertyDefinitions methods are no longer needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-806) JDBC connector handling of convert is inconsistent

by Steven Hawkins (JIRA)

JDBC connector handling of convert is inconsistent -------------------------------------------------- Key: TEIID-806 URL: https://jira.jboss.org/jira/browse/TEIID-806 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3.0 If a source lacks the exact representation of a Teiid type we approximate it with the closest source type. Pushed converts will typically not have the same affect as if they are evaluated in the engine. For example sources lacking byte or tinyint types are having conversions dropped rather, but the actual effect should be modulo the max byte value. We also are not ensuring that the truncation or rounding behavior is the same for all conversions - such as from a floating point number to a fixed point. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1038) SF connector fails to connect.

by John Doyle (JIRA)

SF connector fails to connect. ------------------------------ Key: TEIID-1038 URL: https://jira.jboss.org/jira/browse/TEIID-1038 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.0 Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Changes for JCA including the migration to cxf have some residual issues. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2010