November 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2961) Using JDG CP, unable to create data source without entering AliasCacheName property

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2961?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2961. ------------------------------------ Resolution: Done 10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/2777d5b4b84b0a214... > Using JDG CP, unable to create data source without entering AliasCacheName property > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-2961 > URL: https://issues.jboss.org/browse/TEIIDDES-2961 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 10.0.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Fix For: 10.0.2 > > Attachments: JDGConnectionInfoProvider.patch, JDGProfileDetailsWizardPage.patch > > > Created a JDG connection profile to connect to an existing JDG cache. When I select the create DataSource option, it present a dialog that indicated the AliashCacheName cannot be null. The AliasCacheName and StagingCacheName should be empty if not using materialization. > StackTrace: > java.lang.IllegalArgumentException: No value for the connection property 'AliasCacheName' > at org.teiid.core.designer.util.CoreArgCheck.isNotZeroLength(CoreArgCheck.java:117) > at org.teiid.core.designer.util.CoreArgCheck.isNotEmpty(CoreArgCheck.java:249) > at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:662) > at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:185) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[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 resolved TEIIDDES-2942. ------------------------------------ Resolution: Done 10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/a1aa75325e5d6e5e0... * added type check to prevent exception > 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 > Assignee: Barry LaFond > 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 (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2966) Wrong value is showing in view dialog in source model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2966?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2966. ------------------------------------ Resolution: Done 10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/79c03adb872b249a1... > Wrong value is showing in view dialog in source model > ----------------------------------------------------- > > Key: TEIIDDES-2966 > URL: https://issues.jboss.org/browse/TEIIDDES-2966 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 10.1 > Reporter: Mario Majernik > Assignee: Barry LaFond > Priority: Minor > Fix For: 10.0.2 > > > Wrong value in Length column. Should be there some number but there is some datatype. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2966) Wrong value is showing in view dialog in source model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2966?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2966: -------------------------------------- Assignee: Barry LaFond > Wrong value is showing in view dialog in source model > ----------------------------------------------------- > > Key: TEIIDDES-2966 > URL: https://issues.jboss.org/browse/TEIIDDES-2966 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 10.1 > Reporter: Mario Majernik > Assignee: Barry LaFond > Priority: Minor > Fix For: 10.0.2 > > > Wrong value in Length column. Should be there some number but there is some datatype. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2956) Designer has generated the wrong jar in the JDG module

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2956?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2956: ----------------------------------- Attachment: Book.jar > Designer has generated the wrong jar in the JDG module > ------------------------------------------------------- > > Key: TEIIDDES-2956 > URL: https://issues.jboss.org/browse/TEIIDDES-2956 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.0.2 > Environment: Windows 10 1607 > Reporter: Matej Kralik > Assignee: Barry LaFond > Priority: Blocker > Fix For: 10.0.2 > > Attachments: Book.jar, Book_fedora.jar, Book_windows10.jar, completeJDGproject3.zip, express-zip-contents-on-windows.png, jarInFedora.png, jarInWindows.png > > > I want to deploy dynamic vdb with JDG materialization on the server and server shows me error that: > {code:java} > IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: java.lang.ClassNotFoundException: org.teiid.jdg.pojo.Book from [Module "org.teiid.jdg.pojo:main" from local module loader @16f65612 (finder: local module finder @311d617d (roots: C:\Users\jboss\Downloads\testJDG\EAP-6.4.0\modules,C:\Users\jboss\Downloads\testJDG\EAP-6.4.0\modules\system\layers\dv,C:\Users\jboss\Downloads\testJDG\EAP-6.4.0\modules\system\layers\base\.overlays\layer-base-jboss-eap-6.4.9.CP,C:\Users\jboss\Downloads\testJDG\EAP-6.4.0\modules\system\layers\base))] > {code} > I noticed that something is wrong with generated jar file in the windows because when I use jar file which I generated in the fedora, materialization works fine. I uploaded both jar files. > The strange thing is that when I open .jar (which was generated in the windows ) via 7-file in the windows, file contains folders to Book.class (org/teiid/jdg/pojo) (jarInWindows.png) but when I open this same .jar in the fedora, file contains .class which have name org\teiid\jdg\pojo/Book.class (jarInFedora.png). Maybe this is the problem. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2971) Create Primary Keys when JDG materialization is created

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2971?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2971: ----------------------------------- Fix Version/s: 10.0.2 > Create Primary Keys when JDG materialization is created > ------------------------------------------------------- > > Key: TEIIDDES-2971 > URL: https://issues.jboss.org/browse/TEIIDDES-2971 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 10.0.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 10.0.2 > > > When a view is being materialized for JDG, the following keys need to be created: > - as part of the cacheTypeMap property, the 3rd parameter primary key column: (cacheName:ClassName:primarykeycolumn) > a primary key should be made containing that column on both of the newly created tables. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2970) Set default MatView Extension Properties for JDG materialization

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2970?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2970: ----------------------------------- Fix Version/s: 10.0.2 > Set default MatView Extension Properties for JDG materialization > ---------------------------------------------------------------- > > Key: TEIIDDES-2970 > URL: https://issues.jboss.org/browse/TEIIDDES-2970 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 10.0.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 10.0.2 > > > When a view is being materialized for JDG, set the following extension properties: > <vhalbert> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute {jdgsourcemodelname}.native(''swap cache names'');' > <vhalbert> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute {jdgsourcemodelname}.native(''truncate cache'');', > where {jdgsourcemodelname} as the new JDG Source Model that is created. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2971) Create Primary Keys when JDG materialization is created

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2971?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2971: ----------------------------------- Summary: Create Primary Keys when JDG materialization is created (was: Create Primary Keys when JDG materialization is creatd) > Create Primary Keys when JDG materialization is created > ------------------------------------------------------- > > Key: TEIIDDES-2971 > URL: https://issues.jboss.org/browse/TEIIDDES-2971 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 10.0.2 > Reporter: Van Halbert > Assignee: Barry LaFond > > When a view is being materialized for JDG, the following keys need to be created: > - as part of the cacheTypeMap property, the 3rd parameter primary key column: (cacheName:ClassName:primarykeycolumn) > a primary key should be made containing that column on both of the newly created tables. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2971) Create Primary Keys when JDG materialization is creatd

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2971?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-2971: ---------------------------------- Summary: Create Primary Keys when JDG materialization is creatd (was: Create Primary and Foreign Keys when JDG materialization is created) > Create Primary Keys when JDG materialization is creatd > ------------------------------------------------------ > > Key: TEIIDDES-2971 > URL: https://issues.jboss.org/browse/TEIIDDES-2971 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 10.0.2 > Reporter: Van Halbert > Assignee: Barry LaFond > > When a view is being materialized for JDG, the following keys need to be created: > - as part of the cacheTypeMap property, the 3rd parameter primary key column: (cacheName:ClassName:primarykeycolumn) > a primary key should be made containing that column on both of the newly created tables. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2971) Create Primary and Foreign Keys when JDG materialization is created

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2971?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2971: ----------------------------------- Summary: Create Primary and Foreign Keys when JDG materialization is created (was: Create Primary and Foreign Keys when JDG materialization is creatd) > Create Primary and Foreign Keys when JDG materialization is created > ------------------------------------------------------------------- > > Key: TEIIDDES-2971 > URL: https://issues.jboss.org/browse/TEIIDDES-2971 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 10.0.2 > Reporter: Van Halbert > Assignee: Barry LaFond > > When a view is being materialized for JDG, the following keys need to be created: > - as part of the cacheTypeMap property, the 3rd parameter primary key column: (cacheName:ClassName:primarykeycolumn) > a primary key should be made containing that column on both of the newly created tables. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2016