[JBoss JIRA] (TEIIDDES-2930) Dynamic VDB should contain full path to the materialized table
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2930?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2930:
-----------------------------------
Attachment: screenshotProp.png
> Dynamic VDB should contain full path to the materialized table
> --------------------------------------------------------------
>
> Key: TEIIDDES-2930
> URL: https://issues.jboss.org/browse/TEIIDDES-2930
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: jdgCustomer.zip, screenshot1.png, screenshotProp.png
>
>
> I have a table (CustomerViewMat.Customer) and I set materialized table to another model (CustomerMatCache.Customer) (screenshot1) .I create VDB and dynamic VDB. When I want to deploy this dynamic VDB to the server, server shows me error:
> TEIID31088 The materialization table Customer defined on view CustomerViewMat.Customer, must be defined with "schema" qualifier that represents PHYSICAL model.
> I noticed that in the dynamicVDB in the CustomerViewMat model is:
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'Customer', "teiid_rel: ...
> {code}
> I think that this happens because Customer table is in the CustomerViewMat and CustomerMatCache too. But in the properties (Screenshot1) is set correctly model. (CustomerMatCache)
> When I set full path, vdb was deployed sucessfully
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'CustomerMatCache.Customer', "teiid_rel: ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2930) Dynamic VDB should contain full path to the materialized table
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2930?page=com.atlassian.jira.plu... ]
Matej Kralik reopened TEIIDDES-2930:
------------------------------------
Dynamic VDB now contains full path but the path references to the wrong table. In the properties, table has set correct materialized table (CustomerMatCache.Customer) (screenshotProp) but when I generated dynamic VDB, materialized table was set to wrong model:
{code:java}
MATERIALIZED_TABLE 'CustomerViewMat.Customer'
{code}
Expected
{code:java}
MATERIALIZED_TABLE 'CustomerMatCache.Customer'
{code}
Maybe the problem is that the tables have equal name.
> Dynamic VDB should contain full path to the materialized table
> --------------------------------------------------------------
>
> Key: TEIIDDES-2930
> URL: https://issues.jboss.org/browse/TEIIDDES-2930
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: jdgCustomer.zip, screenshot1.png
>
>
> I have a table (CustomerViewMat.Customer) and I set materialized table to another model (CustomerMatCache.Customer) (screenshot1) .I create VDB and dynamic VDB. When I want to deploy this dynamic VDB to the server, server shows me error:
> TEIID31088 The materialization table Customer defined on view CustomerViewMat.Customer, must be defined with "schema" qualifier that represents PHYSICAL model.
> I noticed that in the dynamicVDB in the CustomerViewMat model is:
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'Customer', "teiid_rel: ...
> {code}
> I think that this happens because Customer table is in the CustomerViewMat and CustomerMatCache too. But in the properties (Screenshot1) is set correctly model. (CustomerMatCache)
> When I set full path, vdb was deployed sucessfully
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'CustomerMatCache.Customer', "teiid_rel: ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 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 resolved TEIIDDES-2818.
------------------------------------
Resolution: Done
10.0.x : https://github.com/Teiid-Designer/teiid-designer/commit/d6a34f8764a0be0f6...
* Enabled Preview Data for materialized Views
* Fixed preview dynamic vdb generation to include model and tables
referenced in the materialized view property
* Fixed dependency analysis to check each virtual layer to add any
additional materialized models/tables
> 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
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2935) Teiid designer doesn't generate materialization staging table correctly
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2935?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2935:
-----------------------------------
Fix Version/s: 10.0.2
> Teiid designer doesn't generate materialization staging table correctly
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2935
> URL: https://issues.jboss.org/browse/TEIIDDES-2935
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: project.zip
>
>
> I have generated JDG module and materialization table. When I created dynamic vdb and deploy to server, server shows me warning that:
> {code:java}
> TEIID21005 Registered Class not found for table ST_Book1, check table name matches a registered class
> {code}
> I noticed that staging table doesn't contain primary_table parameter in the options.
> I think that Teiid designer should add this parameter automatically after generated this tables.
> Actual ddl:
> {code:java}
> <![CDATA[
> CREATE FOREIGN TABLE Book (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> CREATE FOREIGN TABLE ST_Book1 (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> ]]>
> {code}
> Expected ddl:
> {code:java}
> <![CDATA[
> SET NAMESPACE 'http://www.teiid.org/translator/object/2016' AS tns;
> CREATE FOREIGN TABLE Book (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> CREATE FOREIGN TABLE ST_Book1 (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE',"tns:primary_table" 'BookCacheSource.Book')
> ]]>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2935) Teiid designer doesn't generate materialization staging table correctly
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2935?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2935.
------------------------------------
Resolution: Done
Fixed as part of TEIIDDES-2878 & TEIIDDES-2933
10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/9470050514f257f78...
> Teiid designer doesn't generate materialization staging table correctly
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2935
> URL: https://issues.jboss.org/browse/TEIIDDES-2935
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Attachments: project.zip
>
>
> I have generated JDG module and materialization table. When I created dynamic vdb and deploy to server, server shows me warning that:
> {code:java}
> TEIID21005 Registered Class not found for table ST_Book1, check table name matches a registered class
> {code}
> I noticed that staging table doesn't contain primary_table parameter in the options.
> I think that Teiid designer should add this parameter automatically after generated this tables.
> Actual ddl:
> {code:java}
> <![CDATA[
> CREATE FOREIGN TABLE Book (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> CREATE FOREIGN TABLE ST_Book1 (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> ]]>
> {code}
> Expected ddl:
> {code:java}
> <![CDATA[
> SET NAMESPACE 'http://www.teiid.org/translator/object/2016' AS tns;
> CREATE FOREIGN TABLE Book (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> CREATE FOREIGN TABLE ST_Book1 (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE',"tns:primary_table" 'BookCacheSource.Book')
> ]]>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 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.2
(was: 10.0.3)
> 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
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2686) Source Model created via Teiid Connection Import from SalesForce source doesn't work
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2686?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2686:
-----------------------------------
Fix Version/s: 10.0.3
(was: 10.0.2)
> 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
> Assignee: Barry LaFond
> Fix For: 10.0.3
>
>
> 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)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2852) Import from Infinispan issue
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2852?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2852:
----------------------------------------
Not sure the relevance of this until after the JDG features are completed and tested.
On completion of TEIIDDES-2878 and TEIIDDES-2933, I tested the TCI and selected my MateriailzedStock data source. The infinispan-dsl ds type (driver) existed. Clicking NEXT ended up failing with
Caused by: java.lang.ClassCastException: org.teiid.resource.spi.WrappedConnectionFactory cannot be cast to javax.sql.DataSource
Pushing to 10.0.3
> Import from Infinispan issue
> ----------------------------
>
> Key: TEIIDDES-2852
> URL: https://issues.jboss.org/browse/TEIIDDES-2852
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.1
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 10.0.3
>
> Attachments: Screen Shot 2016-06-03 at 15.38.12.png, Screen Shot 2016-06-03 at 15.38.17.png, Screen Shot 2016-06-06 at 14.51.05 (3).png
>
>
> If I want to import from Infinispan (remote-cache) using Teiid Connection import in TD and I have a resource adapter defined like this:
> {code:xml}
> <resource-adapter id="infinispan-remote-cache-ds">
> <module slot="main" id="org.jboss.teiid.resource-adapter.infinispan.dsl"/>
> <transaction-support>LocalTransaction</transaction-support>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.infinispan.dsl.InfinispanManagedConnectionFactory" jndi-name="java:/infinispanRemoteDSL" enabled="true" use-java-context="true" pool-name="infinispan-remote-cache-ds">
> <config-property name="ProtobufDefinitionFile">
> /org/jboss/qe/jdg/remote/protobuf/SmallA.proto
> </config-property>
> <config-property name="RemoteServerList">
> dvqe01.mw.lab.eng.bos.redhat.com:11322
> </config-property>
> <config-property name="MessageMarshallers">
> org.jboss.qe.jdg.pojo.SmallA:org.jboss.qe.jdg.remote.marshaller.SmallAMarshaller
> </config-property>
> <config-property name="CacheTypeMap">
> smallARemotecache:org.jboss.qe.jdg.pojo.SmallA;intKey
> </config-property>
> <config-property name="Module">
> org.jboss.qe.jdg.pojos
> </config-property>
> <config-property name="MessageDescriptor">
> org.jboss.qe.jdg.remote.protobuf.SmallA
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> I am getting this error in TD - see attached screenshot.
> And I cannot continue through the wizard.
> I have to add another resource adapter that works like a driver for the previous one. The configuration looks like this:
> {code:xml}
> <resource-adapter id="infinispan-remote-driver">
> <module slot="main" id="org.jboss.teiid.resource-adapter.infinispan.dsl"/>
> </resource-adapter>
> {code}
> After adding this^ "driver" everything works.
> Is this a TD bug? or is it supposed to work this way ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (TEIIDDES-2852) Import from Infinispan issue
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2852?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2852:
-----------------------------------
Fix Version/s: 10.0.3
> Import from Infinispan issue
> ----------------------------
>
> Key: TEIIDDES-2852
> URL: https://issues.jboss.org/browse/TEIIDDES-2852
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.1
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 10.0.3
>
> Attachments: Screen Shot 2016-06-03 at 15.38.12.png, Screen Shot 2016-06-03 at 15.38.17.png, Screen Shot 2016-06-06 at 14.51.05 (3).png
>
>
> If I want to import from Infinispan (remote-cache) using Teiid Connection import in TD and I have a resource adapter defined like this:
> {code:xml}
> <resource-adapter id="infinispan-remote-cache-ds">
> <module slot="main" id="org.jboss.teiid.resource-adapter.infinispan.dsl"/>
> <transaction-support>LocalTransaction</transaction-support>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.infinispan.dsl.InfinispanManagedConnectionFactory" jndi-name="java:/infinispanRemoteDSL" enabled="true" use-java-context="true" pool-name="infinispan-remote-cache-ds">
> <config-property name="ProtobufDefinitionFile">
> /org/jboss/qe/jdg/remote/protobuf/SmallA.proto
> </config-property>
> <config-property name="RemoteServerList">
> dvqe01.mw.lab.eng.bos.redhat.com:11322
> </config-property>
> <config-property name="MessageMarshallers">
> org.jboss.qe.jdg.pojo.SmallA:org.jboss.qe.jdg.remote.marshaller.SmallAMarshaller
> </config-property>
> <config-property name="CacheTypeMap">
> smallARemotecache:org.jboss.qe.jdg.pojo.SmallA;intKey
> </config-property>
> <config-property name="Module">
> org.jboss.qe.jdg.pojos
> </config-property>
> <config-property name="MessageDescriptor">
> org.jboss.qe.jdg.remote.protobuf.SmallA
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> I am getting this error in TD - see attached screenshot.
> And I cannot continue through the wizard.
> I have to add another resource adapter that works like a driver for the previous one. The configuration looks like this:
> {code:xml}
> <resource-adapter id="infinispan-remote-driver">
> <module slot="main" id="org.jboss.teiid.resource-adapter.infinispan.dsl"/>
> </resource-adapter>
> {code}
> After adding this^ "driver" everything works.
> Is this a TD bug? or is it supposed to work this way ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months