May 2015 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-2519) Teiid Connection Import dialog unusable on lower resolution screens

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2519: ---------------------------------------- Summary: Teiid Connection Import dialog unusable on lower resolution screens Key: TEIIDDES-2519 URL: https://issues.jboss.org/browse/TEIIDDES-2519 Project: Teiid Designer Issue Type: Bug Affects Versions: 9.0.2 Beta1 Reporter: Andrej Šmigala Attachments: teiid-connection-import.png The *Data Source Properties* section of the Teiid Connection import wizard barely shows one line of the table. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2501) Modify dialogs that are deemed too large to use on lower-resolution screens

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2501?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2501: ----------------------------------- Attachment: ddl-import-wizard.png > Modify dialogs that are deemed too large to use on lower-resolution screens > --------------------------------------------------------------------------- > > Key: TEIIDDES-2501 > URL: https://issues.jboss.org/browse/TEIIDDES-2501 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: create-web-service-resized-with-scollbars.png, create-web-service-smaller.png, ddl-import-wizard.png, jdbc_import_1.png, jdbc_import_2.png, jdbc_import_3.png, jdbc_import_4_tab_1.png, jdbc_import_4_tab_2.png > > > Several of Designer's dialogs and wizards are too large to successfully demo on lower-resolution screens. There's a request to modify some of these to reduce the size of the panels/dialogs. Some of this could involve adding scrolling of the outer panel. Others might require re-arranging widgets/sub-panels, adding tab'd panels, etc. > * Transformation's Reconciler Dialog > * Create Web Services dialog > * Salesforce Importer (maybe JDBC Importer) > * ... (TBD) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2395) Add shortcut to Find Model Object in the Model Explorer Tab

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2395?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2395. ------------------------------------ Verified with Teiid Designer 9.0.2 Beta1 > Add shortcut to Find Model Object in the Model Explorer Tab > ----------------------------------------------------------- > > Key: TEIIDDES-2395 > URL: https://issues.jboss.org/browse/TEIIDDES-2395 > Project: Teiid Designer > Issue Type: Feature Request > Components: Editors > Affects Versions: 8.6 > Reporter: Joao Viragine > Assignee: Barry LaFond > Priority: Minor > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > Attachments: find-model-object-in-explorer-toolbar.png > > > It would be nice if we had a shortcut to "Find Model Object" in the Model Explorer Tab. > It isn't productive to need to go to Menu/Search/Teiid Designer/Find Model Object every time we need to serach for a Model Object -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2482) Enable DDL Importer to import Teiid DDL CREATE VIEW statements to capture and set SQL expression in view model

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2482?page=com.atlassian.jira.plu... ] Andrej Šmigala reopened TEIIDDES-2482: -------------------------------------- Importing view now works, but importing procedures does not. Importing the following DDL creates a view procedure with the correct input parameters and result set, but the transformation is empty {code:sql} CREATE VIRTUAL PROCEDURE getParts(p1 biginteger, p2 string) RETURNS (id biginteger, name string) AS BEGIN SELECT PART_ID as id, PART_NAME as name FROM PartsOracle.PARTS WHERE (PART_ID = p1) AND (PART_NAME = p2); END {code} The following error is logged: {noformat} java.lang.Exception: The property definition "relational:non-prepared" could not be found. at org.teiid.designer.core.extension.EmfModelObjectExtensionAssistant.setPropertyValue(EmfModelObjectExtensionAssistant.java:485) at org.teiid.designer.metamodels.relational.extension.RelationalModelExtensionAssistant.setPropertyValue(RelationalModelExtensionAssistant.java:245) at org.teiid.designer.ddl.importer.node.EmfModelGenerator.setPropertyValue(EmfModelGenerator.java:1203) at org.teiid.designer.ddl.importer.node.EmfModelGenerator.processProcedureExtensionProperties(EmfModelGenerator.java:1131) at org.teiid.designer.ddl.importer.node.EmfModelGenerator.processExtensionProperties(EmfModelGenerator.java:1093) at org.teiid.designer.ddl.importer.node.EmfModelGenerator.execute(EmfModelGenerator.java:219) at org.teiid.designer.ddl.importer.DdlImporter.save(DdlImporter.java:324) at org.teiid.designer.ddl.importer.ui.DdlImporterWizard$1.run(DdlImporterWizard.java:123) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:527) at org.teiid.designer.ddl.importer.ui.DdlImporterWizard.finish(DdlImporterWizard.java:116) at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) at org.eclipse.jface.window.Window.open(Window.java:808) at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:158) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) 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:210) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:174) at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:99) at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:170) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) {noformat} > Enable DDL Importer to import Teiid DDL CREATE VIEW statements to capture and set SQL expression in view model > -------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2482 > URL: https://issues.jboss.org/browse/TEIIDDES-2482 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Transformations > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > Attachments: view_example.ddl > > > Teiid DDL supports CREATE VIEW & CREATE PROCEDURE statements that contain SQL expression. The current DDL Importer does not recognize the SQL expression and will not set that value on a table or procedure when importing to a View model. > Make the changes necessary to discover the SQL expression and apply to a virtual table/procedure if importing to a View model. > To Test: > * Select Designer's simple DDL Importer wizard > * Make sure *Teiid* dialect is selected > * Make sure *View* model option is selected -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2482) Enable DDL Importer to import Teiid DDL CREATE VIEW statements to capture and set SQL expression in view model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2482?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2482: ----------------------------------- Description: Teiid DDL supports CREATE VIEW & CREATE PROCEDURE statements that contain SQL expression. The current DDL Importer does not recognize the SQL expression and will not set that value on a table or procedure when importing to a View model. Make the changes necessary to discover the SQL expression and apply to a virtual table/procedure if importing to a View model. To Test: * Select Designer's simple DDL Importer wizard * Make sure *Teiid* dialect is selected * Make sure *View* model option is selected was: Teiid DDL supports CREATE VIEW & CREATE PROCEDURE statements that contain SQL expression. The current DDL Importer does not recognize the SQL expression and will not set that value on a table or procedure when importing to a View model. Make the changes necessary to discover the SQL expression and apply to a virtual table/procedure if importing to a View model. > Enable DDL Importer to import Teiid DDL CREATE VIEW statements to capture and set SQL expression in view model > -------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2482 > URL: https://issues.jboss.org/browse/TEIIDDES-2482 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Transformations > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > Attachments: view_example.ddl > > > Teiid DDL supports CREATE VIEW & CREATE PROCEDURE statements that contain SQL expression. The current DDL Importer does not recognize the SQL expression and will not set that value on a table or procedure when importing to a View model. > Make the changes necessary to discover the SQL expression and apply to a virtual table/procedure if importing to a View model. > To Test: > * Select Designer's simple DDL Importer wizard > * Make sure *Teiid* dialect is selected > * Make sure *View* model option is selected -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2482) Enable DDL Importer to import Teiid DDL CREATE VIEW statements to capture and set SQL expression in view model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2482?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2482: ----------------------------------- Attachment: view_example.ddl > Enable DDL Importer to import Teiid DDL CREATE VIEW statements to capture and set SQL expression in view model > -------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2482 > URL: https://issues.jboss.org/browse/TEIIDDES-2482 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Transformations > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > Attachments: view_example.ddl > > > Teiid DDL supports CREATE VIEW & CREATE PROCEDURE statements that contain SQL expression. The current DDL Importer does not recognize the SQL expression and will not set that value on a table or procedure when importing to a View model. > Make the changes necessary to discover the SQL expression and apply to a virtual table/procedure if importing to a View model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2337) Add Swagger UI to Expose VDB RESTFul Procedures

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2337?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2337. ------------------------------------ Verified with Teiid Designer 9.0.2 Beta1 > Add Swagger UI to Expose VDB RESTFul Procedures > ----------------------------------------------- > > Key: TEIIDDES-2337 > URL: https://issues.jboss.org/browse/TEIIDDES-2337 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.6 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > > Should investigate adding Swagger to expose RESTFul procedures in a given VDB. > http://swagger.io/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2379) A view should not be allowed to set the materialization target to itself

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2379?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2379. ------------------------------------ Verified with Teiid Designer 9.0.2 Beta1 > A view should not be allowed to set the materialization target to itself > ------------------------------------------------------------------------ > > Key: TEIIDDES-2379 > URL: https://issues.jboss.org/browse/TEIIDDES-2379 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6 > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > > A user inadvertently set the materialization target to itself and received a recursive planning exception at runtime. Designer should prevent this if possible (ideally it would prevent any materialization target that results in a cycle). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2440) No proper column mapping for second primary key in view model

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2440?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2440. ------------------------------------ Verified with Teiid Designer 9.0.2 Beta1 > No proper column mapping for second primary key in view model > ------------------------------------------------------------- > > Key: TEIIDDES-2440 > URL: https://issues.jboss.org/browse/TEIIDDES-2440 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.3.4, 8.6 > Environment: Windows > Reporter: Endy Brosens > Assignee: Barry LaFond > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > Attachments: property-not-supported.png, TEIIDDES-2440-workaround.png > > > I have a source relational model where some entities I want to expose via OData REST don't have a primary key. As you know, teiid OData support will not expose a given entity via REST unless the entity has either a primary key or unique constraint defined. > > I also have a view model defined where i transform some entity names to make them more REST API resource model "friendly". This view model is also where I want to define some primary keys for entities in the source model that don't have primary keys. > > I can define a primary key set on one given entity in my view model, but when I try to define a primary key set on a second entity in the view model the columns that are available for selection are those related to the first given entity I defined a primary key for. It would seem that one should only be able to select columns that are associated with the entity you're working with. > > This occurs on teiid designer 8.3.4.Final, 8.6, teiid 8.7, on windows. > The workaround is to edit the View Model in the Standard Eclipse XML Editor and assign column GUID's to the Primary Key XML element. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2436) StackOverflow Exception Importing VDB via JDBC Importer

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2436?page=com.atlassian.jira.plu... ] Andrej Šmigala reopened TEIIDDES-2436: -------------------------------------- Reopening this issue. The StackOverflow is gone, but now the dialog is very confusing. When trying to import the VDB, it seems that *Show all schema* is selected, along with *Show only selected schema*, however, no schemas are shown and there is an error saying 'At least one object must be selected for import' (see screenshot). This can be remedied by clicking on *Show all schema* (even though it is already selected), but as I said, it is very confusing. > StackOverflow Exception Importing VDB via JDBC Importer > ------------------------------------------------------- > > Key: TEIIDDES-2436 > URL: https://issues.jboss.org/browse/TEIIDDES-2436 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > Attachments: import-vdb.png, JdbcImoprtObjectsPage_TEIIDDES_2436.patch > > > Receiving StackOverflow exception importing a VDB via the JDBC importer using the following steps: > 1. Import a JDBC source (any source) > a. On page 3, select "Show Selected Schemas". > 2. Now try importing a deployed VDB. You will receive a StackOverflow exception. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2015