July 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1786) Update query metadata interface for update to teiid 8.5 interface

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1786?page=com.atlassian.jira.plu... ] Barry LaFond moved TEIID-2585 to TEIIDDES-1786: ----------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-1786 (was: TEIID-2585) Issue Type: Task (was: Quality Risk) Component/s: (was: Query Engine) Fix Version/s: 8.3 (was: 8.5) > Update query metadata interface for update to teiid 8.5 interface > ----------------------------------------------------------------- > > Key: TEIIDDES-1786 > URL: https://issues.jboss.org/browse/TEIIDDES-1786 > Project: Teiid Designer > Issue Type: Task > Reporter: Barry LaFond > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.3 > > > Parsed objects retain much of the original parse string, which is generally unnecessary on the server side. The use of output names should reduced to unnecessary memory consumption. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1767) Cannot redeploy a vdb with webservice datasource

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1767?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1767: ----------------------------------- Fix Version/s: 8.2 > Cannot redeploy a vdb with webservice datasource > ------------------------------------------------ > > Key: TEIIDDES-1767 > URL: https://issues.jboss.org/browse/TEIIDDES-1767 > Project: Teiid Designer > Issue Type: Bug > Reporter: Paul Richardson > Assignee: Ted Jones > Fix For: 8.2 > > > When redeploying a vdb that contains a WSDL webservice, the following behaviour is observed. > 1. Delete all vdb's data sources, including the WSDL webservice data source; > 2. Deploy the vdb > 3. Observe the following error > {code} > !ENTRY org.teiid.designer.dqp.ui 4 0 2013-06-27 10:18:06.314 > !MESSAGE TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered > !STACK 0 > org.teiid.adminapi.AdminProcessingException: TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered > at org.teiid.adminapi.AdminFactory$ResultCallback.onFailure(AdminFactory.java:195) > at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1409) > at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:277) > at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412) > at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324) > at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551) > at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107) > at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:239) > at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:286) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > {code} > Despite 'StockQuote' being deleted in step 1, the JBoss server still has it cached in a map so throws back this error. The client does not show it and connecting to the server via the cli also fails to show it. Restarting the server flushes the cache and the vdb can be successfully redeployed. > Whether this should be passed to Teiid (are they responsible for flushing the cache?) or WireFly (not properly flushing the cache or data source deletion) is the question... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1785) JBT Integration Stack Issues

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1785: ----------------------------------------- Summary: JBT Integration Stack Issues Key: TEIIDDES-1785 URL: https://issues.jboss.org/browse/TEIIDDES-1785 Project: Teiid Designer Issue Type: Bug Components: Release Work Affects Versions: 8.2 Reporter: Paul Richardson Assignee: Paul Richardson Fix For: 8.2 Umbrella JIRA for integration-stack related issues. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1548) Add GUI handling for permission conditions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1548?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1548. ------------------------------------ Resolution: Done Done > Add GUI handling for permission conditions > ------------------------------------------ > > Key: TEIIDDES-1548 > URL: https://issues.jboss.org/browse/TEIIDDES-1548 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 8.2 > > Attachments: add-allowed-language-dialog.png, add-column-mask-dialog.png, add-row-based-security-dialog.png, allowed-languages-tab.png, column-mask-tab.png, row-based-security-tab.png > > > A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose: > <permission> > <resource-name>...</resource-name> > <condition>sql</condition> > ... > </permission> > The sql should resolve against the resource specified, ideally designer would check that as well. > See TEIID-2311 and the reference for how these conditions are applied. > {code:title=vdb.xml snippet} > <data-role name="base-role" any-authenticated="true"> > <description>Conditional access</description> > > <permission> > <resource-name>modelName.tblName</resource-name> > <condition constraint="false">column1=user()</condition> > </permission> > > </data-role> > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1655) Teiid importer needs to handle schema and catalog cases for generated model

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1655?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1655. ------------------------------------- Resolution: Done Cleaned up entity naming. Also addressed a problem where PKs were not being generated correctly in the StandardImporter. https://github.com/Teiid-Designer/teiid-designer/pull/208 > Teiid importer needs to handle schema and catalog cases for generated model > --------------------------------------------------------------------------- > > Key: TEIIDDES-1655 > URL: https://issues.jboss.org/browse/TEIIDDES-1655 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > When importing via the Teiid Importer, an example of Teiid DDL for tables: > CREATE FOREIGN TABLE "accounts.ACCOUNT" ( > COL1 long NOT NULL DEFAULT '0' OPTIONS (..., NAMEINSOURCE '`ACCOUNT_ID`', ...), > ) OPTIONS (..., NAMEINSOURCE '`accounts`.`ACCOUNT`', ...); > Since some dbs support catalogs, the 'dotted' names can be multiple levels deep. We need to use a combination of NameInSource and potentially filtering on the DDL retrieval to determine how the model entities are to be created. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1784) Selecting individual tables in Teiid Connection importer still results in all tables being imported

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1784?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1784. ------------------------------------- Resolution: Done fixed issues with TreeViewerController - was not updating the checkbox states correctly. https://github.com/Teiid-Designer/teiid-designer/pull/207 > Selecting individual tables in Teiid Connection importer still results in all tables being imported > --------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1784 > URL: https://issues.jboss.org/browse/TEIIDDES-1784 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 8.2 > > > I imported from a Parts SQL Server DB which exposed standard parts tables and system tables. > De-selected all but parts tables, but all tables were generated. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1610) Unresolved references in transformation column mappings after moving source model in project

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1610?page=com.atlassian.jira.plu... ] Lucie Fabrikova commented on TEIIDDES-1610: ------------------------------------------- I created a relational view model from existing relational source model, with use of "Transform from an existing Model optional builder". If I delete a column from a table in view model, I get error: "Sql transformation in the model ViewModel contains the unresolved reference Books2.xmi". > Unresolved references in transformation column mappings after moving source model in project > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1610 > URL: https://issues.jboss.org/browse/TEIIDDES-1610 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.0, 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: TestRefactorMoveMPS_8.x.zip > > > * Import attached model project set > * Select Products source model in sources folder > * Right-select the Refactor > Move action > * Select the root project location for the move and FINISH > * Multiple validation errors are created like: > Sql transformation in the model ProductViews contains the unresolved reference file:/home/blafond/Development/Designer/runtime-workspaces/8.1_A/TestRefactorMove/Products.xmi ProductViews.xmi /TestRefactorMove/views Container/SQL Transformation Mapping Root/Mapping -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1779) Designer error when trying to read a remote server configuration that's running in domain mode

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1779?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1779: ------------------------------------------- Given that JBT is declaring domain mode unsupported, its unsurprising that things are not working. See [https://issues.jboss.org/browse/JBIDE-14592]. I think until JBT has domain mode fully supported there is no way that designer's tools could reliably try and get it working. > Designer error when trying to read a remote server configuration that's running in domain mode > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1779 > URL: https://issues.jboss.org/browse/TEIIDDES-1779 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Paul Richardson > Priority: Blocker > > org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [{"subsystem" => "teiid"}]. Failure was "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"teiid\")]". > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336) > at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:58) > at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.getTeiidRuntimeVersion(JBoss7ServerUtil.java:172) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.createJboss7TeiidServer(TeiidServerAdapterFactory.java:204) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:185) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:78) > at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:66) > at org.eclipse.wst.server.core.internal.ResourceManager.fireServerEvent(ResourceManager.java:560) > at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:712) > at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:474) > at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:266) > at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:463) > at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:432) > at org.eclipse.wst.server.ui.internal.editor.ServerEditor.doSave(ServerEditor.java:389) > at org.eclipse.ui.internal.DefaultSaveable.doSave(DefaultSaveable.java:54) > at org.eclipse.ui.Saveable.doSave(Saveable.java:214) > at org.eclipse.ui.internal.SaveableHelper.doSaveModel(SaveableHelper.java:348) > at org.eclipse.ui.internal.WorkbenchPage$11.run(WorkbenchPage.java:3633) > at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:276) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) > at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:1812) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1809) > at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:284) > at org.eclipse.ui.internal.WorkbenchPage.saveAll(WorkbenchPage.java:3644) > at org.eclipse.ui.internal.WorkbenchPage.saveAllEditors(WorkbenchPage.java:3440) > at org.eclipse.ui.internal.handlers.SaveAllHandler.execute(SaveAllHandler.java:47) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) > 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.Display.sendEvent(Display.java:4166) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > 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:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > 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:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [{"subsystem" => "teiid"}]. Failure was "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"teiid\")]". > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:327) > ... 76 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1784) Selecting individual tables in Teiid Connection importer still results in all tables being imported

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1784?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1784: ----------------------------------- Fix Version/s: 8.2 > Selecting individual tables in Teiid Connection importer still results in all tables being imported > --------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1784 > URL: https://issues.jboss.org/browse/TEIIDDES-1784 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 8.2 > > > I imported from a Parts SQL Server DB which exposed standard parts tables and system tables. > De-selected all but parts tables, but all tables were generated. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1784) Selecting individual tables in Teiid Connection importer still results in all tables being imported

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1784: -------------------------------------- Summary: Selecting individual tables in Teiid Connection importer still results in all tables being imported Key: TEIIDDES-1784 URL: https://issues.jboss.org/browse/TEIIDDES-1784 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Barry LaFond Assignee: Mark Drilling I imported from a Parts SQL Server DB which exposed standard parts tables and system tables. De-selected all but parts tables, but all tables were generated. -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2013