[JBoss JIRA] (TEIIDDES-2942) Procedure input parameter has result in the generated DDL
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2942?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2942:
------------------------------------------
> So the exporter will treat OUT's as straight OUT parameters and if a RETURN parameter exists, then it'll be treated as an OUT parameter with a "result" added.
Yes, that is correct.
> Procedure input parameter has result in the generated DDL
> ---------------------------------------------------------
>
> Key: TEIIDDES-2942
> URL: https://issues.jboss.org/browse/TEIIDDES-2942
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.2
>
> Attachments: ddlProject.zip
>
>
> I have a procedure with one input parameter. When I want to preview this procedure or deploy dynamic VDB, server shows me error that:
> {code:java}
> TEIID31100 Parsing error: Encountered "(4000) [*]result[*]) RETURNS" at line 2, column 52.
> Procedure testProc RESULT param p1 must be of type OUT.
> {code}
> I noticed that generated dynamic VDB contains 'result' in this parameter but this parameter has set direction to IN. When I delete the result from dynamic VDB, the procedure works fine.
> Actual DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000) result) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
> expected DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2942) Procedure input parameter has result in the generated DDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2942?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2942 at 10/20/16 3:31 PM:
------------------------------------------------------------------
[~shawkins] So Designer allows a) and b) above.
* A procedure can only have have 1 out parameter marked as a return
Designer has 4 direction options: OUT, INOUT, OUT and RETURN, so there's no way to set an OUT parameter to be returned. There can only be 1 RETURN parameter, else validation ERROR
So the exporter will treat OUT's as straight OUT parameters and if a RETURN parameter exists, then it'll be treated as an OUT parameter with a "result" added.
Lastly.. if a Result Set does NOT exist and a RETURN parameter exists... we have the option to either export the parameter and NO RESULT SET, or.... use the RETURN parameter info and export a RESULT SET with a single column and datatype? Should we NOT do the latter?
was (Author: blafond):
[~shawkins] So Designer allows a) and b) above.
* A procedure can only have have 1 out parameter marked as a return
Designer has 4 direction options: OUT, INOUT, OUT and RETURN, so there's no way to set an OUT parameter to be returned. There can only be 1 RETURN parameter, else validation ERROR
So the exporter will treat OUT's as straight OUT parameters and if a RETURN parameter exists, then it'll be treated as an OUT parameter with a "result" added.
> Procedure input parameter has result in the generated DDL
> ---------------------------------------------------------
>
> Key: TEIIDDES-2942
> URL: https://issues.jboss.org/browse/TEIIDDES-2942
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.2
>
> Attachments: ddlProject.zip
>
>
> I have a procedure with one input parameter. When I want to preview this procedure or deploy dynamic VDB, server shows me error that:
> {code:java}
> TEIID31100 Parsing error: Encountered "(4000) [*]result[*]) RETURNS" at line 2, column 52.
> Procedure testProc RESULT param p1 must be of type OUT.
> {code}
> I noticed that generated dynamic VDB contains 'result' in this parameter but this parameter has set direction to IN. When I delete the result from dynamic VDB, the procedure works fine.
> Actual DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000) result) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
> expected DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2942) Procedure input parameter has result in the generated DDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2942?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2942:
----------------------------------------
[~shawkins] So Designer allows a) and b) above.
* A procedure can only have have 1 out parameter marked as a return
Designer has 4 direction options: OUT, INOUT, OUT and RETURN, so there's no way to set an OUT parameter to be returned. There can only be 1 RETURN parameter, else validation ERROR
So the exporter will treat OUT's as straight OUT parameters and if a RETURN parameter exists, then it'll be treated as an OUT parameter with a "result" added.
> Procedure input parameter has result in the generated DDL
> ---------------------------------------------------------
>
> Key: TEIIDDES-2942
> URL: https://issues.jboss.org/browse/TEIIDDES-2942
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.2
>
> Attachments: ddlProject.zip
>
>
> I have a procedure with one input parameter. When I want to preview this procedure or deploy dynamic VDB, server shows me error that:
> {code:java}
> TEIID31100 Parsing error: Encountered "(4000) [*]result[*]) RETURNS" at line 2, column 52.
> Procedure testProc RESULT param p1 must be of type OUT.
> {code}
> I noticed that generated dynamic VDB contains 'result' in this parameter but this parameter has set direction to IN. When I delete the result from dynamic VDB, the procedure works fine.
> Actual DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000) result) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
> expected DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2927) Connection to remote DV doesn't work
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2927?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2927:
-----------------------------------
Comment: was deleted
(was: [~gadeyne.bram] Can you add which versions of Teiid you are trying to connect to?)
> Connection to remote DV doesn't work
> ------------------------------------
>
> Key: TEIIDDES-2927
> URL: https://issues.jboss.org/browse/TEIIDDES-2927
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.1
> Reporter: Bram Gadeyne
> Priority: Blocker
>
> Hi,
> I'm using teiiddesigner 10.1 and teiid server 9.0.4.
> I could connect to teiid in the past from the designer 10.1 (I think it was to 9.0.2 when I originally created the connection). I always see this error in the logs:
> java.lang.IllegalArgumentException: admin
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:302)
> at org.teiid.runtime.client.admin.ExecutionAdmin.<init>(ExecutionAdmin.java:124)
> at org.teiid.runtime.client.admin.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:53)
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:90)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:243)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:259)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:197)
> at java.lang.Thread.run(Thread.java:745)
> And a second one later on:
> java.lang.IllegalArgumentException: admin
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:302)
> at org.teiid.runtime.client.admin.ExecutionAdmin.<init>(ExecutionAdmin.java:124)
> at org.teiid.runtime.client.admin.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:53)
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:90)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:243)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293)
> at org.teiid.designer.runtime.ui.server.SetDefaultServerAction$1.run(SetDefaultServerAction.java:196)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.SetDefaultServerAction.run(SetDefaultServerAction.java:191)
> at org.teiid.designer.runtime.ui.server.SetDefaultServerAction.execute(SetDefaultServerAction.java:285)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> 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:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> 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.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:330)
> at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$6.linkActivated(ModelExplorerResourceNavigator.java:711)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
> 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:498)
> 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)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2927) Connection to remote DV doesn't work
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2927?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2927:
----------------------------------------
[~gadeyne.bram] Can you add which versions of Teiid you are trying to connect to?
> Connection to remote DV doesn't work
> ------------------------------------
>
> Key: TEIIDDES-2927
> URL: https://issues.jboss.org/browse/TEIIDDES-2927
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.1
> Reporter: Bram Gadeyne
> Priority: Blocker
>
> Hi,
> I'm using teiiddesigner 10.1 and teiid server 9.0.4.
> I could connect to teiid in the past from the designer 10.1 (I think it was to 9.0.2 when I originally created the connection). I always see this error in the logs:
> java.lang.IllegalArgumentException: admin
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:302)
> at org.teiid.runtime.client.admin.ExecutionAdmin.<init>(ExecutionAdmin.java:124)
> at org.teiid.runtime.client.admin.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:53)
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:90)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:243)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:259)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:197)
> at java.lang.Thread.run(Thread.java:745)
> And a second one later on:
> java.lang.IllegalArgumentException: admin
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:302)
> at org.teiid.runtime.client.admin.ExecutionAdmin.<init>(ExecutionAdmin.java:124)
> at org.teiid.runtime.client.admin.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:53)
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:90)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:243)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293)
> at org.teiid.designer.runtime.ui.server.SetDefaultServerAction$1.run(SetDefaultServerAction.java:196)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.SetDefaultServerAction.run(SetDefaultServerAction.java:191)
> at org.teiid.designer.runtime.ui.server.SetDefaultServerAction.execute(SetDefaultServerAction.java:285)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> 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:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> 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.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:330)
> at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$6.linkActivated(ModelExplorerResourceNavigator.java:711)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
> 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:498)
> 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)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2942) Procedure input parameter has result in the generated DDL
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2942?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2942:
------------------------------------------
- A procedure can have both a return and a result set.
- A procedure can have any number of out, in, in/out parameters
- A procedure can only have have 1 out parameter marked as a return
> Procedure input parameter has result in the generated DDL
> ---------------------------------------------------------
>
> Key: TEIIDDES-2942
> URL: https://issues.jboss.org/browse/TEIIDDES-2942
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.2
>
> Attachments: ddlProject.zip
>
>
> I have a procedure with one input parameter. When I want to preview this procedure or deploy dynamic VDB, server shows me error that:
> {code:java}
> TEIID31100 Parsing error: Encountered "(4000) [*]result[*]) RETURNS" at line 2, column 52.
> Procedure testProc RESULT param p1 must be of type OUT.
> {code}
> I noticed that generated dynamic VDB contains 'result' in this parameter but this parameter has set direction to IN. When I delete the result from dynamic VDB, the procedure works fine.
> Actual DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000) result) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
> expected DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2942) Procedure input parameter has result in the generated DDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2942?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2942 at 10/20/16 2:44 PM:
------------------------------------------------------------------
[~shawkins] So in Designer
1) we have both OUT and RETURN directions and they should behave just as an OUT direction
2) can there be multiple OUT/RETURN parameters or just one?
3) an OUT direction adds the *result* to the parameter
4) A Procedure can have both an OUT parameter AND a Result Set
was (Author: blafond):
[~shawkins] So in Designer
1) we have both OUT and RETURN directions and they should behave just as an OUT direction
2) an OUT direction adds the *result* to the parameter
3) A Procedure can have both an OUT parameter AND a Result Set
> Procedure input parameter has result in the generated DDL
> ---------------------------------------------------------
>
> Key: TEIIDDES-2942
> URL: https://issues.jboss.org/browse/TEIIDDES-2942
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.2
>
> Attachments: ddlProject.zip
>
>
> I have a procedure with one input parameter. When I want to preview this procedure or deploy dynamic VDB, server shows me error that:
> {code:java}
> TEIID31100 Parsing error: Encountered "(4000) [*]result[*]) RETURNS" at line 2, column 52.
> Procedure testProc RESULT param p1 must be of type OUT.
> {code}
> I noticed that generated dynamic VDB contains 'result' in this parameter but this parameter has set direction to IN. When I delete the result from dynamic VDB, the procedure works fine.
> Actual DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000) result) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
> expected DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2938) Escape single quotes in the ANNOTATION string
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2938?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2938:
------------------------------------------
He's saying the descriptions needs to be treated as a string literal - single quotes need to be escaped with another single quote.
> Escape single quotes in the ANNOTATION string
> ---------------------------------------------
>
> Key: TEIIDDES-2938
> URL: https://issues.jboss.org/browse/TEIIDDES-2938
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Reporter: Ramesh Reddy
>
> When reading metadata from TEIID, when ANNOTATION property in the OPTIONS clause comes with escaped string for single quotes it needs to be preserved. Otherwise you will see errors like
> {code}
> 09:06:36,945 WARN [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50036 VDB PREVIEW-1d551d3c-afa8-4eb9-8447-33175b1bdd14.1 model "ClouderaImpalaJDBCConnection" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ", ANNOTATION 'Any query with '[*]select[*]' in it will return this table.')" at line 12, column 86.
> Was expecting: "," | ")": org.teiid.metadata.ParseException: TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ", ANNOTATION 'Any query with '[*]select[*]' in it will return this table.')" at line 12, column 86.
> Was expecting: "," | ")"
> at org.teiid.query.parser.QueryParser.parseDDL(QueryParser.java:472) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.metadata.MetadataFactory.parse(MetadataFactory.java:768) [teiid-api-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.metadata.DDLMetadataRepository.loadMetadata(DDLMetadataRepository.java:40) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.runtime.AbstractVDBDeployer$MetadataRepositoryWrapper.loadMetadata(AbstractVDBDeployer.java:84) [teiid-runtime-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ", ANNOTATION 'Any query with '[*]select[*]' in it will return this table.')" at line 12, column 86.
> Was expecting: "," | ")"
> at org.teiid.query.parser.QueryParser.convertParserException(QueryParser.java:214) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> ... 11 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2942) Procedure input parameter has result in the generated DDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2942?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2942:
----------------------------------------
[~shawkins] So in Designer
1) we have both OUT and RETURN directions and they should behave just as an OUT direction
2) an OUT direction adds the *result* to the parameter
3) A Procedure can have both an OUT parameter AND a Result Set
> Procedure input parameter has result in the generated DDL
> ---------------------------------------------------------
>
> Key: TEIIDDES-2942
> URL: https://issues.jboss.org/browse/TEIIDDES-2942
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.2
>
> Attachments: ddlProject.zip
>
>
> I have a procedure with one input parameter. When I want to preview this procedure or deploy dynamic VDB, server shows me error that:
> {code:java}
> TEIID31100 Parsing error: Encountered "(4000) [*]result[*]) RETURNS" at line 2, column 52.
> Procedure testProc RESULT param p1 must be of type OUT.
> {code}
> I noticed that generated dynamic VDB contains 'result' in this parameter but this parameter has set direction to IN. When I delete the result from dynamic VDB, the procedure works fine.
> Actual DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000) result) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
> expected DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2942) Procedure input parameter has result in the generated DDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2942?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2942:
----------------------------------------
[~shawkins] So in Designer
1) we have both OUT and RETURN directions and they should behave just as an OUT direction
2) an OUT direction adds the *result* to the parameter
3) A Procedure can have both an OUT parameter AND a Result Set
> Procedure input parameter has result in the generated DDL
> ---------------------------------------------------------
>
> Key: TEIIDDES-2942
> URL: https://issues.jboss.org/browse/TEIIDDES-2942
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.2
>
> Attachments: ddlProject.zip
>
>
> I have a procedure with one input parameter. When I want to preview this procedure or deploy dynamic VDB, server shows me error that:
> {code:java}
> TEIID31100 Parsing error: Encountered "(4000) [*]result[*]) RETURNS" at line 2, column 52.
> Procedure testProc RESULT param p1 must be of type OUT.
> {code}
> I noticed that generated dynamic VDB contains 'result' in this parameter but this parameter has set direction to IN. When I delete the result from dynamic VDB, the procedure works fine.
> Actual DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000) result) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
> expected DDL:
> {code:java}
> CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out;
> END;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months