[JBoss JIRA] (TEIIDDES-2355) Provide an option to import pushdown functions
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2355?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2355:
-----------------------------------
Fix Version/s: 10.0.3
(was: 10.0.2)
> Provide an option to import pushdown functions
> ----------------------------------------------
>
> Key: TEIIDDES-2355
> URL: https://issues.jboss.org/browse/TEIIDDES-2355
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 10.0.3
>
> Attachments: pushDown.zip
>
>
> The import property importer.importPushdownFunctions can be set to have Teiid include the pushdown functions as part of the imported schema and there by the ddl used by designer. With TEIID-3098 will prevent there from being ambiguity from doing so (either from multiple models or from the pushdown functions). So Designer should allow users to import these functions if they wish (it could even be a default option).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2993) Eclipse/Designer extension to export a model project as dynamic VDBs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2993?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2993:
------------------------------------------
Moving to the Designer side to capture if there are any more requirements/options, such as generating a vdb zip, and/or saving the ddl along side the .xmi files. Note that there are several issues with the current ddl export approach around ddl generation and default options including TEIIDDES-2699
> Eclipse/Designer extension to export a model project as dynamic VDBs
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2993
> URL: https://issues.jboss.org/browse/TEIIDDES-2993
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> Request is following forum ref https://developer.jboss.org/message/965470 . As a consumer we have built extensive structures in Designer (static) VDBs. We would like a tool either standalone or in Designer/Eclipse that would export a model project as proper dynamic virtual databases. Example is included in the forum.
> If this tool becomes on the roadmap I will file a jira to request a feature to optimize the dynamic VDB through the use of VDB imports to eliminate redundancy in a project.
> In this single project we estimate that this will save us 1 person, two 2-week sprints.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2993) Eclipse/Designer extension to export a model project as dynamic VDBs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2993?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-4585 to TEIIDDES-2993:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-2993 (was: TEIID-4585)
Component/s: Teiid Integration
(was: Tools)
> Eclipse/Designer extension to export a model project as dynamic VDBs
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2993
> URL: https://issues.jboss.org/browse/TEIIDDES-2993
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> Request is following forum ref https://developer.jboss.org/message/965470 . As a consumer we have built extensive structures in Designer (static) VDBs. We would like a tool either standalone or in Designer/Eclipse that would export a model project as proper dynamic virtual databases. Example is included in the forum.
> If this tool becomes on the roadmap I will file a jira to request a feature to optimize the dynamic VDB through the use of VDB imports to eliminate redundancy in a project.
> In this single project we estimate that this will save us 1 person, two 2-week sprints.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2993) Eclipse/Designer extension to export a model project as dynamic VDBs
by Don Krapohl (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2993?page=com.atlassian.jira.plu... ]
Don Krapohl closed TEIIDDES-2993.
---------------------------------
Resolution: Rejected
Feature exists as noted in the forum. On the VDB click on Modeling->generate dynamic VDB.
> Eclipse/Designer extension to export a model project as dynamic VDBs
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2993
> URL: https://issues.jboss.org/browse/TEIIDDES-2993
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> Request is following forum ref https://developer.jboss.org/message/965470 . As a consumer we have built extensive structures in Designer (static) VDBs. We would like a tool either standalone or in Designer/Eclipse that would export a model project as proper dynamic virtual databases. Example is included in the forum.
> If this tool becomes on the roadmap I will file a jira to request a feature to optimize the dynamic VDB through the use of VDB imports to eliminate redundancy in a project.
> In this single project we estimate that this will save us 1 person, two 2-week sprints.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2818) preview on view that uses another view that is materialized fails
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2818?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2818:
-----------------------------------
Fix Version/s: 10.0.3
(was: 10.0.2)
> preview on view that uses another view that is materialized fails
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2818
> URL: https://issues.jboss.org/browse/TEIIDDES-2818
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 9.0.6
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 10.0.3
>
>
> If you mark a view table(view.table1) materialized true, the preview option is grayed out as it should be, but if you then create another view table(view.table2) that uses the above materialized view table, the preview option is available but errors with:
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.api.exception.query.QueryPlannerException: Group does not exist: view.table1
> We should document this that this is not possible and/or a better error description would be nice and/or disable the preview data option for a view model which is based on view model which has materialized set to true.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2818) preview on view that uses another view that is materialized fails
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2818?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-2818:
----------------------------------------
[~apodhrad], [~blafond] I retested today to be sure on how it works right now. I found out that if you set materialized - true on view table Preview is not gray out and you get exception:
{code:java}
java.lang.IllegalArgumentException: Expected argument to be non-null but got null
at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
at org.teiid.designer.core.workspace.ModelUtil.getModel(ModelUtil.java:251)
at org.teiid.designer.runtime.preview.DependentObjectHelper.addMaterializedTables(DependentObjectHelper.java:132)
at org.teiid.designer.runtime.preview.DependentObjectHelper.findSourceTables(DependentObjectHelper.java:123)
at org.teiid.designer.runtime.preview.DependentObjectHelper.calculateDependentObjects(DependentObjectHelper.java:86)
at org.teiid.designer.runtime.preview.DependentObjectHelper.<init>(DependentObjectHelper.java:74)
at org.teiid.designer.runtime.preview.PreviewManager.getVdbSourceModelInfos(PreviewManager.java:588)
at org.teiid.designer.runtime.preview.PreviewManager.createDynamicVdb(PreviewManager.java:352)
at org.teiid.designer.runtime.preview.PreviewManager.generateDynamicVdb(PreviewManager.java:132)
at org.teiid.designer.runtime.preview.PreviewManager.getDynamicVdbStatus(PreviewManager.java:107)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker.internalRun(PreviewDataWorker.java:327)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker.run(PreviewDataWorker.java:209)
at org.teiid.designer.runtime.ui.preview.PreviewTableDataContextAction.run(PreviewTableDataContextAction.java:99)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
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:4230)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
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:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
{code}
> preview on view that uses another view that is materialized fails
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2818
> URL: https://issues.jboss.org/browse/TEIIDDES-2818
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 9.0.6
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
>
> If you mark a view table(view.table1) materialized true, the preview option is grayed out as it should be, but if you then create another view table(view.table2) that uses the above materialized view table, the preview option is available but errors with:
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.api.exception.query.QueryPlannerException: Group does not exist: view.table1
> We should document this that this is not possible and/or a better error description would be nice and/or disable the preview data option for a view model which is based on view model which has materialized set to true.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2818) preview on view that uses another view that is materialized fails
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2818?page=com.atlassian.jira.plu... ]
Matus Makovy reopened TEIIDDES-2818:
------------------------------------
> preview on view that uses another view that is materialized fails
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2818
> URL: https://issues.jboss.org/browse/TEIIDDES-2818
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 9.0.6
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
>
> If you mark a view table(view.table1) materialized true, the preview option is grayed out as it should be, but if you then create another view table(view.table2) that uses the above materialized view table, the preview option is available but errors with:
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.api.exception.query.QueryPlannerException: Group does not exist: view.table1
> We should document this that this is not possible and/or a better error description would be nice and/or disable the preview data option for a view model which is based on view model which has materialized set to true.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2818) preview on view that uses another view that is materialized fails
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2818?page=com.atlassian.jira.plu... ]
Andrej Podhradsky commented on TEIIDDES-2818:
---------------------------------------------
Hi [~blafond], please set other fix version since 10.0.2 has been already released.
> preview on view that uses another view that is materialized fails
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2818
> URL: https://issues.jboss.org/browse/TEIIDDES-2818
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 9.0.6
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
>
> If you mark a view table(view.table1) materialized true, the preview option is grayed out as it should be, but if you then create another view table(view.table2) that uses the above materialized view table, the preview option is available but errors with:
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.api.exception.query.QueryPlannerException: Group does not exist: view.table1
> We should document this that this is not possible and/or a better error description would be nice and/or disable the preview data option for a view model which is based on view model which has materialized set to true.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2991) Cannot generate REST war in TD
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2991?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2991:
--------------------------------------
Assignee: Ted Jones (was: Barry LaFond)
> Cannot generate REST war in TD
> ------------------------------
>
> Key: TEIIDDES-2991
> URL: https://issues.jboss.org/browse/TEIIDDES-2991
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: MAC
> Reporter: Matus Makovy
> Assignee: Ted Jones
> Priority: Critical
> Fix For: 10.0.3
>
> Attachments: project.zip
>
>
> When I right click the VDB and select Modeling -> generate REST WAR I get this excetption:
> {code:java}
> java.lang.Exception: no suitable method found for create(org.teiid.query.parser.TeiidParser,org.teiid.query.parser.TeiidNodeFactory.ASTNodes)
> method org.teiid.query.parser.TeiidNodeFactory.<T>create(org.teiid.designer.runtime.version.spi.ITeiidServerVersion,org.teiid.query.parser.TeiidNodeFactory.ASTNodes) is not applicable
> (cannot infer type-variable(s) T
> (argument mismatch; org.teiid.query.parser.TeiidParser cannot be converted to org.teiid.designer.runtime.version.spi.ITeiidServerVersion))
> method org.teiid.query.parser.TeiidNodeFactory.<T>create(org.teiid.designer.runtime.version.spi.ITeiidServerVersion,int) is not applicable
> (cannot infer type-variable(s) T
> (argument mismatch; org.teiid.query.parser.TeiidParser cannot be converted to org.teiid.designer.runtime.version.spi.ITeiidServerVersion))
> at org.teiid.designer.runtime.ui.wizards.webservices.util.RestWebArchiveBuilderImpl.createResourceJavaClasses(RestWebArchiveBuilderImpl.java:608)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.RestWebArchiveBuilderImpl.createWebArchive(RestWebArchiveBuilderImpl.java:226)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.execute(RestWarDeploymentInfoDialog.java:214)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog$1.run(RestWarDeploymentInfoDialog.java:169)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:500)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.okPressed(RestWarDeploymentInfoDialog.java:178)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:466)
> 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:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.teiid.designer.runtime.ui.wizards.webservices.RestWarDeploymentInfoDialog.open(RestWarDeploymentInfoDialog.java:190)
> at org.teiid.designer.runtime.ui.actions.GenerateRestWarAction.run(GenerateRestWarAction.java:150)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> 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:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> 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:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
> Project attached.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months