April 2010 - teiid-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (TEIID-1078) Build annotation based configuration for the Connector Translation layer

by Ramesh Reddy (JIRA)

Build annotation based configuration for the Connector Translation layer ------------------------------------------------------------------------- Key: TEIID-1078 URL: https://jira.jboss.org/jira/browse/TEIID-1078 Project: Teiid Issue Type: Sub-task Components: Connector API Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Since the Translation layer in no longer a JCA, the properties that are specific to Translation layer need to be modified into annotation based properties backed JAXB based beans. These properties need to exposed through "templates" for the 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
2
0 / 0

[JBoss JIRA] Created: (TEIID-1056) Required Connector Properties Should Have A Default Value If They Are Marked As An Expert Property

by Dan Florian (JIRA)

Required Connector Properties Should Have A Default Value If They Are Marked As An Expert Property -------------------------------------------------------------------------------------------------- Key: TEIID-1056 URL: https://jira.jboss.org/jira/browse/TEIID-1056 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 7.0 Environment: Teiid 7.0 M3, Ubuntu 9.04 Reporter: Dan Florian Assignee: Steven Hawkins Fix For: 7.0 The JDBC connector's "connection-definition" property is marked as an expert property but does not have a default value. Expert properties generally require very little maintenance and are normally not presented initially to a user. If a default value cannot be assigned to a required property it should not be marked as "expert." There might be other connectors with similar 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

6
6
0 / 0

[JBoss JIRA] Created: (TEIID-1046) Component Name of the VDB is null through Profile Service

by Ramesh Reddy (JIRA)

Component Name of the VDB is null through Profile Service --------------------------------------------------------- Key: TEIID-1046 URL: https://jira.jboss.org/jira/browse/TEIID-1046 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 When the VDB is accessed using the profile service, the component name is null. This makes impossible to search for component by its name. With out this the search must be done using component type. -- 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
7
0 / 0

[JBoss JIRA] Created: (TEIID-1071) Modify validation errors element in schema for VDB configuration file to include attribute for location of error

by John Verhaeg (JIRA)

Modify validation errors element in schema for VDB configuration file to include attribute for location of error ---------------------------------------------------------------------------------------------------------------- Key: TEIID-1071 URL: https://jira.jboss.org/jira/browse/TEIID-1071 Project: Teiid Issue Type: Feature Request Affects Versions: 6.2.0 Reporter: John Verhaeg Assignee: Steven Hawkins Fix For: 7.0 The Designer needs this information to allow the user to navigate to the offending object within a model. So, we either need a specific attribute for location, or a generic properties element like within the model and entry elements -- 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-943) Fully implement client streaming of lobs/readers/streams

by Steven Hawkins (JIRA)

Fully implement client streaming of lobs/readers/streams -------------------------------------------------------- Key: TEIID-943 URL: https://jira.jboss.org/jira/browse/TEIID-943 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1 Client transmission of large objects is either not implemented or is implemented through fully materializing. We should instead allow for streaming backed by temp files on the server. -- 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-1045) Provide a admin method to "export" a Data Source.

by Ramesh Reddy (JIRA)

Provide a admin method to "export" a Data Source. ------------------------------------------------- Key: TEIID-1045 URL: https://jira.jboss.org/jira/browse/TEIID-1045 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 7.0 As of 7.0 M3, there is no admin method to export a data source that is defined inside the AS. This needs to be supported for the tooling purposes. Also, the "addDataSource" only supports to create XA data sources. It should also allow to create "local" data sources. -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2010