June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1137) DB2 Import - Source with DECIMAL datatype is being imported as LONG

by Warren Gibson (JIRA)

DB2 Import - Source with DECIMAL datatype is being imported as LONG ------------------------------------------------------------------- Key: TEIID-1137 URL: https://jira.jboss.org/browse/TEIID-1137 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 7.1 Reporter: Warren Gibson Assignee: Steve Hawkins Importer for DB2 is importing BQT2 LONGNUM (DECIMAL in database) to a LONG after import. Steve H says this should be come in as either a BigInteger or BigDecimal. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-177) Provide JDBC 3.0 JRE 1.5 backwards compatibility

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-177?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins commented on TEIID-177: ------------------------------------- I should mention that the retro approach has the drawback that we do not get compile time safety as with the comment based approach. Errors are only noticeable when executing. The advantage though is that we won't have to mark up our code and we can make it to 1.4 support. > Provide JDBC 3.0 JRE 1.5 backwards compatibility > ------------------------------------------------ > > Key: TEIID-177 > URL: https://jira.jboss.org/browse/TEIID-177 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 7.1 > > > The jdbc driver needs to support jdk 1.5 on the client. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-208) LDAP Connector should implement Connection.isAlive(), in order to properly report connection status when monitored

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-208?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-208. ------------------------------- > LDAP Connector should implement Connection.isAlive(), in order to properly report connection status when monitored > ------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-208 > URL: https://jira.jboss.org/browse/TEIID-208 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Priority: Minor > Fix For: 7.0 > > > Connection.isAlive is currently implemented to always return "true". This means that connection status is not accurately reflected in the Console, and connection monitoring is not useful. We should implement this method, which may also require establishing a connection in the pool upon startup. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1017) Move defining the Data Roles to VDB deployer XML file. Map the roles to container roles

by Ramesh Reddy (JIRA)

Move defining the Data Roles to VDB deployer XML file. Map the roles to container roles --------------------------------------------------------------------------------------- Key: TEIID-1017 URL: https://jira.jboss.org/jira/browse/TEIID-1017 Project: Teiid Issue Type: Sub-task Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Previously in Teiid, in order to define data roles for a VDB, the were defined in a file called "data-roles.xml" and that file used to be included with the VDB artifact. Move the definition and contents of this file in vdb.xml (see TEIID-998) Given a "data role" at design time, the user should be able to map this role to a "container" role. Give ability in the Admin API to update this role mapping. -- 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-358) Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing

by Paul Nittel (JIRA)

Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing -------------------------------------------------------------------------------- Key: TEIID-358 URL: https://jira.jboss.org/jira/browse/TEIID-358 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 6.0.0 Environment: fedora 10 Reporter: Paul Nittel Assignee: Steven Hawkins I ran into this while assisting user Bribek. When the Derby source is created and imported, a connector binding is built in the Designer. The one thing Designer does not do is place the jar file where it needs to be for previewing. The Quick Start Example needs to add the step of adding the derbyclient.jar file using the UDFs view and "Import UDF Extension Jar Files" action. IMHO, the Quick Start needs to be revisited to determine exactly what the required minimum effort is for a user to get through this. Perhaps on the Teiid side avoid all modeling and add a Quick Start on the Designer side that builds the VDB. If Teiid can do the Quick Start with just a VDB, that might be preferable. -- 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

5
9
0 / 0

[JBoss JIRA] Created: (TEIID-901) NPE encountered when doing an INSERT into SFDC Account table

by Mark Drilling (JIRA)

NPE encountered when doing an INSERT into SFDC Account table ------------------------------------------------------------ Key: TEIID-901 URL: https://jira.jboss.org/jira/browse/TEIID-901 Project: Teiid Issue Type: Bug Components: Salesforce Connector Reporter: Mark Drilling Assignee: John Doyle Attempt to insert record into the SDFC account table failed with the following exception: Caused by: java.lang.NullPointerException at com.metamatrix.connector.salesforce.execution.visitors.InsertVisitor.stripQutes(InsertVisitor.java:64) at com.metamatrix.connector.salesforce.execution.visitors.InsertVisitor.visit(InsertVisitor.java:44) at com.metamatrix.connector.salesforce.execution.InsertExecutionImpl.execute(InsertExecutionImpl.java:15) at com.metamatrix.connector.salesforce.execution.UpdateExecutionParent.execute(UpdateExecutionParent.java:67) -- 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-1127) java.lang.ClassCastException Executing Virtual Procedure from Web Service Model

by Ted Jones (JIRA)

java.lang.ClassCastException Executing Virtual Procedure from Web Service Model ------------------------------------------------------------------------------- Key: TEIID-1127 URL: https://jira.jboss.org/browse/TEIID-1127 Project: Teiid Issue Type: Bug Components: JDBC Driver Reporter: Ted Jones Assignee: Steve Hawkins Fix For: 7.0 Getting a Teiid connection via JNDI and executing the query (exec Books_MySql_WS.Books_MySql_BOOKS.getBOOKS();) results in the following java.lang.ClassCastException error: 10:51:59,143 ERROR [PROCESSOR] Unexpected exception for request qGFm7nWIemY9.3 java.lang.ClassCastException: org.jboss.resource.adapter.jdbc.WrapperDataSource cannot be cast to java.sql.Connection at org.teiid.translator.jdbc.JDBCExecutionFactory.createResultSetExecution(JDBCExecutionFactory.java:79) at org.teiid.translator.ExecutionFactory.createExecution(ExecutionFactory.java:193) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.execute(ConnectorWorkItem.java:250) at org.teiid.dqp.internal.process.DataTierTupleSource.open(DataTierTupleSource.java:118) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:82) at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:136) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:260) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:106) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:157) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:107) at org.teiid.query.processor.BatchIterator.hasNext(BatchIterator.java:80) at org.teiid.query.processor.xml.RelationalPlanExecutor.execute(RelationalPlanExecutor.java:98) at org.teiid.query.processor.xml.ExecSqlInstruction.process(ExecSqlInstruction.java:59) at org.teiid.query.processor.xml.XMLPlan.nextBatch(XMLPlan.java:158) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:157) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:107) at org.teiid.query.processor.BatchIterator.hasNext(BatchIterator.java:80) at org.teiid.query.processor.proc.ProcedurePlan.executePlan(ProcedurePlan.java:440) at org.teiid.query.processor.proc.CreateCursorResultSetInstruction.process(CreateCursorResultSetInstruction.java:67) at org.teiid.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:293) at org.teiid.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:232) at org.teiid.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:114) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:260) at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:168) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:260) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:106) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:157) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:107) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:67) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:250) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:177) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:190) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:187) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:176) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:187) 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) -- 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

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-995) The management console should support deploying VDB to EDS

by Van Halbert (JIRA)

The management console should support deploying VDB to EDS ---------------------------------------------------------- Key: TEIID-995 URL: https://jira.jboss.org/jira/browse/TEIID-995 Project: Teiid Issue Type: Task Components: Jopr Plugin Affects Versions: 7.1 Reporter: Van Halbert Assignee: Ted Jones Fix For: 7.1 The management console should support deploying VDB to EDS, and subsequently, enable the establishment of a JDBC connection from a client application to EDS using the same 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

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1029) Provide sample scripts that show the use of the AdminAPI in an alternative scripting manner

by Van Halbert (JIRA)

Provide sample scripts that show the use of the AdminAPI in an alternative scripting manner ------------------------------------------------------------------------------------------- Key: TEIID-1029 URL: https://jira.jboss.org/jira/browse/TEIID-1029 Project: Teiid Issue Type: Feature Request Components: AdminApi, Build/Kits Reporter: Van Halbert Assignee: Steven Hawkins Fix For: 7.1 Sample administrative scripts should be provided for common tasks that show the use of the AdminAPI in an alternative script manner. -- 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-1039) Provide a solution to 'merge' two VDBs

by Ramesh Reddy (JIRA)

Provide a solution to 'merge' two VDBs --------------------------------------- Key: TEIID-1039 URL: https://jira.jboss.org/jira/browse/TEIID-1039 Project: Teiid Issue Type: Feature Request Components: AdminApi, Server Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Based on the conversation on this thread http://lists.jboss.org/pipermail/teiid-designer-dev/2010-March/000212.html Teiid and Designer needs a mechanism, where child VDB can be merged into parent VDB. Designer can use this mechanism to provide the preview functionality. -- 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 June 2010