December 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2706) Constraint value ignored in Row Filter dialog

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2706?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2706: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1277068|https://bugzilla.redhat.com/show_bug.cgi?id=1277068] from NEW to CLOSED > Constraint value ignored in Row Filter dialog > --------------------------------------------- > > Key: TEIIDDES-2706 > URL: https://issues.jboss.org/browse/TEIIDDES-2706 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Andrej Šmigala > Priority: Minor > Fix For: 9.2.1 > > Attachments: Screenshot from 2015-11-02 10-00-55.png, Screenshot from 2015-11-02 10-01-07.png > > > When adding a new row filter, unchecking the Constraint checkbox in the Add Row Filter Definition dialog does not set the constraint property to false. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2697) Virtual procedure in generated dynamic VDB does not return result set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2697?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2697: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1273832|https://bugzilla.redhat.com/show_bug.cgi?id=1273832] from NEW to CLOSED > Virtual procedure in generated dynamic VDB does not return result set > --------------------------------------------------------------------- > > Key: TEIIDDES-2697 > URL: https://issues.jboss.org/browse/TEIIDDES-2697 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2 > > Attachments: DynamicProcedureProject.zip > > > When a VDB containing view model with a virtual procedure is exported as a dynamic VDB, the virtual procedure does not return any results. This is because the generated DDL does not contain the RETURNS clause. > Generated DDL: > {code:sql} > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) > AS > BEGIN > SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; > END; > {code} > Expected DDL: > {code:sql} > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE ( xml_out xml) > 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)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2695) Deployed dynamic VDB not shown in server views

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2695?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2695: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1273458|https://bugzilla.redhat.com/show_bug.cgi?id=1273458] from NEW to CLOSED > Deployed dynamic VDB not shown in server views > ---------------------------------------------- > > Key: TEIIDDES-2695 > URL: https://issues.jboss.org/browse/TEIIDDES-2695 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Reporter: Andrej Šmigala > > When a dynamic VDB (created from a VDB archive) is deployed on the server, it is not shown in the list of VDBs in the Servers view, only after refreshing the server. Suggesting to show it immediately after deploying, like with regular VDBs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2698) REST procedure in generated dynamic VDB does not work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2698?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2698: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1273841|https://bugzilla.redhat.com/show_bug.cgi?id=1273841] from NEW to CLOSED > REST procedure in generated dynamic VDB does not work > ----------------------------------------------------- > > Key: TEIIDDES-2698 > URL: https://issues.jboss.org/browse/TEIIDDES-2698 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Extension Framework, VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Fix For: 9.2.1 > > Attachments: DynamicProcedureProject.zip > > > When a VDB containing view model with a REST procedure is exported as a dynamic VDB, the resulting autogenrated WAR does not work. This is because the generated DDL does not contain the OPTIONS clause with REST properties, nor does it contain the required SET NAMESPACE statement > Generated DDL: > {code:sql} > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) > AS > BEGIN > SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; > END; > {code} > Expected DDL (note that this also incorporates TEIIDDES-2697): > {code:sql} > SET NAMESPACE 'http://teiid.org/rest' AS REST; > 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)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2689) LDAP dialogue too slow - loads a lot of data?

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2689?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2689: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1271639|https://bugzilla.redhat.com/show_bug.cgi?id=1271639] from NEW to CLOSED > LDAP dialogue too slow - loads a lot of data? > --------------------------------------------- > > Key: TEIIDDES-2689 > URL: https://issues.jboss.org/browse/TEIIDDES-2689 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0.4 > Environment: MAC OS > Reporter: Matus Makovy > Assignee: Paul Richardson > Priority: Critical > Fix For: 9.2.1 > > Attachments: Screen Shot 2015-10-14 at 14.17.46.png > > > I came across this when trying to verify TEIIDDES-2478. > When you have a LDAP instance with big amount of entries (in the screenshot you can see that are 931 entries) in some part, it takes long to load all attributes. After clicking Next> on the page shown in screenshot (see attachment) JBDS freezes and doesn't respond for about 3 minutes. At least we should have some message that says, that TD is loading data from LDAP. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2694) Generate Web Service Translator Procedures - description of procedures needs update

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2694?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2694: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1273014|https://bugzilla.redhat.com/show_bug.cgi?id=1273014] from NEW to CLOSED > Generate Web Service Translator Procedures - description of procedures needs update > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-2694 > URL: https://issues.jboss.org/browse/TEIIDDES-2694 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Assignee: Matus Makovy > Priority: Minor > Fix For: 9.2 > > Attachments: Screen Shot 2015-10-19 at 13.45.46.png > > > Fix for TEIIDDES-2329 added new parameter for invokeHttp() procedure. This needs to be added in the description in this dialogue. See screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2692) Operation editor still show that SQL is invalid but it is valid.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2692?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2692: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1272104|https://bugzilla.redhat.com/show_bug.cgi?id=1272104] from NEW to CLOSED > Operation editor still show that SQL is invalid but it is valid. > ---------------------------------------------------------------- > > Key: TEIIDDES-2692 > URL: https://issues.jboss.org/browse/TEIIDDES-2692 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Validation > Affects Versions: 9.0.4 > Environment: Fedora 22 > Reporter: Matej Kralik > Priority: Minor > Attachments: ProductsProject.zip, Snímka obrazovky z 2015-10-15 15-50-28.png > > > I rename incorrect name in xml document to correct. When I try validate SQL in the web operation, nothing happend. As soon as I freely adjusted SQL in the operation, validate is correct. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2691) Teiid Connection Import does not set translator when importing from Sybase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2691?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2691: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1271699|https://bugzilla.redhat.com/show_bug.cgi?id=1271699] from NEW to CLOSED > Teiid Connection Import does not set translator when importing from Sybase > -------------------------------------------------------------------------- > > Key: TEIIDDES-2691 > URL: https://issues.jboss.org/browse/TEIIDDES-2691 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Minor > Fix For: 9.2 > > Attachments: Screenshot from 2015-10-14 15-53-23.png > > > When using Teiid Connection to import from Sybase, the translator is set to jdbc-ansi, not sybase. For other relational databases, it is set to the correct translator automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2686) Source Model created via Teiid Connection Import from SalesForce source doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2686?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2686: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1271084|https://bugzilla.redhat.com/show_bug.cgi?id=1271084] from NEW to CLOSED > Source Model created via Teiid Connection Import from SalesForce source doesn't work > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-2686 > URL: https://issues.jboss.org/browse/TEIIDDES-2686 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Environment: MAC OS > Reporter: Matus Makovy > > When I am trying to import from SalesForce using Teiid Connection Import, resulting model doesn't work properly. Querying VDB that includes this model results in: > {noformat} > java.sql.SQLException: org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: null > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:729) > at org.teiid.jdbc.StatementImpl.access$2(StatementImpl.java:715) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:566) > at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:134) > at org.teiid.client.util.ResultsFuture.access$3(ResultsFuture.java:130) > at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:78) > at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:263) > at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:301) > at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:109) > at com.sun.proxy.$Proxy52.read(Unknown Source) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:400) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:575) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:444) > at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:378) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.StatementAdapter.executeQuery(StatementAdapter.java:73) > at org.eclipse.datatools.sqltools.data.internal.core.editor.TableDataImpl.<init>(TableDataImpl.java:158) > at org.eclipse.datatools.sqltools.data.internal.ui.editor.TableDataEditor.createPartControl(TableDataEditor.java:110) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:141) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:327) > 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:888) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:869) > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:120) > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:337) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:258) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:104) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:73) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:55) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:127) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:983) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:662) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:766) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:737) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:731) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:715) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:95) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:4732) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:218) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) > at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) > at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) > at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) > at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:81) > at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59) > at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) > at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:488) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:454) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:705) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:392) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1145) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3210) > at org.eclipse.ui.internal.WorkbenchPage.access$23(WorkbenchPage.java:3125) > at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3107) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3102) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3066) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3047) > at org.eclipse.datatools.sqltools.data.internal.ui.editor.EditTableDataAction.run(EditTableDataAction.java:63) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:519) > 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:4199) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4042) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3669) > 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: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:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > Caused by: org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: null > at org.teiid.client.ResultsMessage.readExternal(ResultsMessage.java:278) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1842) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1799) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) > at org.teiid.net.socket.Message.readExternal(Message.java:54) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1842) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1799) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) > at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.readObjectOverride(ObjectDecoderInputStream.java:118) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365) > at org.teiid.net.socket.OioOjbectChannelFactory$OioObjectChannel.read(OioOjbectChannelFactory.java:113) > ... 103 more > Caused by: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: null > at org.teiid.client.ResultsMessage.setException(ResultsMessage.java:194) > at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:999) > at org.teiid.dqp.internal.process.RequestWorkItem.close(RequestWorkItem.java:556) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:352) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException: Remote java.lang.NullPointerException: null > at org.teiid.translator.salesforce.execution.visitors.CriteriaVisitor.loadColumnMetadata(CriteriaVisitor.java:380) > at org.teiid.translator.salesforce.execution.visitors.SelectVisitor.visit(SelectVisitor.java:137) > at org.teiid.language.NamedTable.acceptVisitor(NamedTable.java:66) > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNodes(AbstractLanguageVisitor.java:63) > at org.teiid.translator.salesforce.execution.visitors.SelectVisitor.visit(SelectVisitor.java:55) > at org.teiid.language.Select.acceptVisitor(Select.java:103) > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) > at org.teiid.translator.salesforce.execution.QueryExecutionImpl.execute(QueryExecutionImpl.java:151) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:329) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) > ... 6 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2697) Virtual procedure in generated dynamic VDB does not return result set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2697?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2697: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1271233|https://bugzilla.redhat.com/show_bug.cgi?id=1271233] from ASSIGNED to CLOSED > Virtual procedure in generated dynamic VDB does not return result set > --------------------------------------------------------------------- > > Key: TEIIDDES-2697 > URL: https://issues.jboss.org/browse/TEIIDDES-2697 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2 > > Attachments: DynamicProcedureProject.zip > > > When a VDB containing view model with a virtual procedure is exported as a dynamic VDB, the virtual procedure does not return any results. This is because the generated DDL does not contain the RETURNS clause. > Generated DDL: > {code:sql} > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) > AS > BEGIN > SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; > END; > {code} > Expected DDL: > {code:sql} > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE ( xml_out xml) > 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)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2015