September 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1478) Modify JDBC import relational processor to tag model as a VDB source model

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1478: -------------------------------------- Summary: Modify JDBC import relational processor to tag model as a VDB source model Key: TEIIDDES-1478 URL: https://issues.jboss.org/browse/TEIIDDES-1478 Project: Teiid Designer Issue Type: Sub-task Components: Import/Export, Modeling Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 8.0 Modify the JDBC import processor to identify connection is a Teiid VDB source, then inject appropriate tags/extension info into the model to identify it as a VDB Source Model. *Add VDB name and version as extension data to Model Annotation ** Need to be aware of this new extension data on MS sequencing? *Create VdbSourceModelExtensionHandler class that can peek into ModelResource/IFile and check to see if it's a VDB Source Model as well as inject extension data (See use of ResourceAnnotationHelper class for connection info) -- 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

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] (TEIIDDES-1486) Create Data Source is broken with Teiid 8.x changes

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1486: -------------------------------------- Summary: Create Data Source is broken with Teiid 8.x changes Key: TEIIDDES-1486 URL: https://issues.jboss.org/browse/TEIIDDES-1486 Project: Teiid Designer Issue Type: Bug Components: Datatools Integration, Teiid Integration, VDB & Execution Reporter: Barry LaFond Assignee: Mark Drilling Priority: Blocker Fix For: 8.0 Teiid 8.x changes resulted in loosing our mapping of simple connection types to known Teiid connection names. Hardcoded constants in DatasourceConnectionConstants were: {code} String JDBC = "connector-jdbc"; //$NON-NLS-1$ String SALESFORCE = "connector-salesforce"; //$NON-NLS-1$ String LDAP = "connector-ldap"; //$NON-NLS-1$ String FILE = "connector-file"; //$NON-NLS-1$ String JDBC_XA = "connector-jdbc-xa"; //$NON-NLS-1$ String WS = "connector-ws"; //$NON-NLS-1$ String UNKNOWN = "connector-unknown"; //$NON-NLS-1$ {code} In 8.x, Teiid data source types are named mostly by their driver jars: while in debug, my current list was: * teiid-local * teiid-connector-file.rar * teiid * teiid-connector-salesforce.rar * teiid-connector-ldap.rar * teiid-connector-ws.rar * ojdbc6.jar * h2 Also changed the type name of "connector-jdbc" in debug to "ojdbc6.jar" and it successfully created a data source on teiid. Need use driver jar from Connection Profile properties. Note, that CP's are allowed to use "multiple driver jars??" -- 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

12 years, 3 months

4
7
0 / 0

[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1118. ------------------------------------- Resolution: Done commit additional fix for handling windows UNC path issue. avoids conversion of EMF and java.net URI altogether due to UNC path issues. > Add/Remove operations on a VDB should block other operations on the VDB > ----------------------------------------------------------------------- > > Key: TEIIDDES-1118 > URL: https://issues.jboss.org/browse/TEIIDDES-1118 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Marc Shirley > Assignee: Mark Drilling > Fix For: 8.0, 7.7.2 > > > As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception: > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435) > at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244) > at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709) > at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) > at org.eclipse.equinox.launcher.Main.run(Main.java:1408) > at org.eclipse.equinox.launcher.Main.main(Main.java:1384) -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1490) Fix VDB Deployment issues

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1490: --------------------------------------- Summary: Fix VDB Deployment issues Key: TEIIDDES-1490 URL: https://issues.jboss.org/browse/TEIIDDES-1490 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 8.0 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.0 VDB Deployment and execution needs to be verified and corrected. -- 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

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] (TEIIDDES-1488) CLONE - Add support for function based indexes on materialized views

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1488?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-2203 to TEIIDDES-1488: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-1488 (was: TEIID-2203) Component/s: Teiid Integration (was: Query Engine) Fix Version/s: (was: 8.2) > CLONE - Add support for function based indexes on materialized views > -------------------------------------------------------------------- > > Key: TEIIDDES-1488 > URL: https://issues.jboss.org/browse/TEIIDDES-1488 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Teiid materialized views should support function based indexes to improve performance. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1222) Convert Function Metamodel to built-in relational model MED

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1222: -------------------------------------- Summary: Convert Function Metamodel to built-in relational model MED Key: TEIIDDES-1222 URL: https://issues.jboss.org/browse/TEIIDDES-1222 Project: Teiid Designer Issue Type: Sub-task Reporter: Barry LaFond In order to retire the Function metamodel we need to replace it with extension properties on the relational metamodel via the new MED framework. in 7.5/7.6 the "Source Function" property (deterministic) is the only current built-in "relational" extended property. Probably could convert to use only 1 built-in MED that extends "Relational" metamodel. -- 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

12 years, 3 months

2
5
0 / 0

[JBoss JIRA] (TEIIDDES-1487) Failure to access Oracle data source with column names enclosed in double quotes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1487?page=com.atlassian.jira.plu... ] Steven Hawkins updated TEIIDDES-1487: ------------------------------------- Assignee: (was: Steven Hawkins) Affects Version/s: 7.4 (was: 7.4.4) Teiid is simply using the nameInSource property to form the source query and does not attempt to detect when quotes are needed. I thought that we (working with Dan) had previously modified the JDBC importer to always use identifier quoting (the dynamic vdb importer works this way already). > Failure to access Oracle data source with column names enclosed in double quotes > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1487 > URL: https://issues.jboss.org/browse/TEIIDDES-1487 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.4 > Environment: EDS 5.2.0 > Reporter: Hisanobu Okuda > > EDS is throwing an error when accessing Oracle data source with column names enclosed in double quotes. I am able to import the metadata, test through Datasource explorer but when i run the query against VDB, it is not interpreting correctly to send double-quotes to the column name in this case, causing below error. > For example, > 1. create table and views as shown below in Oracle database > {code} > create table test(recno number, ref_no varchar2(4000)); > create or replace view test_v as select recno as "Rec_Item_Number", ref_no as "bom_ref_no." from test; > {code} > 2. Import test_v data source view into JBoss developer studio > 3. deploy and run the query against TEST_V:- > Then, the following exception is thrown:- > {code} > 2012-09-05 08:34:39,386 WARN [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) Connector worker process failed for atomic-request=Imx1VPWhia7G.6.0.0 > org.teiid.translator.jdbc.JDBCExecutionException: Error Code:1747 Message:'ORA-01747: invalid user.table.column, table.column, or column specification > ' error executing statement(s): [Prepared Values: [] SQL: SELECT c_0, c_1 FROM (SELECT g_0.Rec_Item_Number AS c_0, g_0.bom_ref_no. AS c_1 FROM "EII_CACHE"."TEST_V" g_0) WHERE ROWNUM <= 100] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:276) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:354) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:143) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:140) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:240) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292) > 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) > Caused by: java.sql.SQLSyntaxErrorException: ORA-01747: invalid user.table.column, table.column, or column specification > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) > at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879) > at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450) > at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192) > at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) > at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207) > at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:884) > at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167) > at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289) > at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3584) > at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3628) > at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1493) > at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:86) > ... 13 more > {code} -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1487) Failure to access Oracle data source with column names enclosed in double quotes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1487?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-2192 to TEIIDDES-1487: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-1487 (was: TEIID-2192) Affects Version/s: 7.4.4 (was: 7.4.4) Component/s: Teiid Integration (was: JDBC Connector) > Failure to access Oracle data source with column names enclosed in double quotes > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1487 > URL: https://issues.jboss.org/browse/TEIIDDES-1487 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.4.4 > Environment: EDS 5.2.0 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > > EDS is throwing an error when accessing Oracle data source with column names enclosed in double quotes. I am able to import the metadata, test through Datasource explorer but when i run the query against VDB, it is not interpreting correctly to send double-quotes to the column name in this case, causing below error. > For example, > 1. create table and views as shown below in Oracle database > {code} > create table test(recno number, ref_no varchar2(4000)); > create or replace view test_v as select recno as "Rec_Item_Number", ref_no as "bom_ref_no." from test; > {code} > 2. Import test_v data source view into JBoss developer studio > 3. deploy and run the query against TEST_V:- > Then, the following exception is thrown:- > {code} > 2012-09-05 08:34:39,386 WARN [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) Connector worker process failed for atomic-request=Imx1VPWhia7G.6.0.0 > org.teiid.translator.jdbc.JDBCExecutionException: Error Code:1747 Message:'ORA-01747: invalid user.table.column, table.column, or column specification > ' error executing statement(s): [Prepared Values: [] SQL: SELECT c_0, c_1 FROM (SELECT g_0.Rec_Item_Number AS c_0, g_0.bom_ref_no. AS c_1 FROM "EII_CACHE"."TEST_V" g_0) WHERE ROWNUM <= 100] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:276) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:354) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:143) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:140) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:240) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292) > 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) > Caused by: java.sql.SQLSyntaxErrorException: ORA-01747: invalid user.table.column, table.column, or column specification > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) > at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879) > at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450) > at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192) > at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) > at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207) > at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:884) > at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167) > at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289) > at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3584) > at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3628) > at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1493) > at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:86) > ... 13 more > {code} -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1372) Mass format the codebase

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1372: ----------------------------------------- Summary: Mass format the codebase Key: TEIIDDES-1372 URL: https://issues.jboss.org/browse/TEIIDDES-1372 Project: Teiid Designer Issue Type: Task Reporter: Paul Richardson Assignee: Paul Richardson Priority: Minor Fix For: 8.0 Mass format the codebase to conform to a single formatting standard. This will ensure that a migration to git will minimize commit patch confusion. -- 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

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1469) SecurityType / userName / password / WsdlURI not included when using 'Set Connection Profile' action

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1469: ----------------------------------------- Summary: SecurityType / userName / password / WsdlURI not included when using 'Set Connection Profile' action Key: TEIIDDES-1469 URL: https://issues.jboss.org/browse/TEIIDDES-1469 Project: Teiid Designer Issue Type: Bug Components: Web Services Support Affects Versions: 7.7.1 Reporter: Paul Richardson Assignee: Paul Richardson Priority: Critical Fix For: 7.7.2 The Set Connection Profile action does not add the following properties from a WS SOAP Connection Profile: * wsdlURI * securityType * username * password The security credentials would just be a nuisance since the securityType in the deployed -ds.xml would be set to 'None' so could be edited. However, the lack of wsdlURI means that the data source xmi is invalid and a containing vdb will not deploy. -- 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

12 years, 3 months

2
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2012