October 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2650) Changing Fields in several dialogues Causes Designer to Hang

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2650?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2650. ---------------------------------- All mentioned dialogues are working. Couple of notes: View Procedure -> Result set - I am still able to edit the name inline, but it is not causing TD to hang anymore. translator name in VDB Editor - I am also able to edit the value here - but it is not causing the designer to hang anymore. > Changing Fields in several dialogues Causes Designer to Hang > ------------------------------------------------------------ > > Key: TEIIDDES-2650 > URL: https://issues.jboss.org/browse/TEIIDDES-2650 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release > Affects Versions: 9.0.3 > Environment: MAC OS X > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.3 > Fix For: 10.0.2 > > > This issue still occurs in several other dialogues on MAC OS X. > * Create Relational View Table -> Columns > * Create Relational View Procedure -> Result Set (+ I am able to edit values in row, without using "Edit" button) > * Create Relational Table -> Colums > * Create Relational Procedure -> Parameters, Result Set > * Create Relational Source Function -> Parameters > * Create Relational Native Query Procedure -> Parameters, Result Set > * Create Relational View -> Columns > * Changing translator in VDB Editor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2650) Changing Fields in several dialogues Causes Designer to Hang

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2650?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2650: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.3 (was: ) > Changing Fields in several dialogues Causes Designer to Hang > ------------------------------------------------------------ > > Key: TEIIDDES-2650 > URL: https://issues.jboss.org/browse/TEIIDDES-2650 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release > Affects Versions: 9.0.3 > Environment: MAC OS X > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.3 > Fix For: 10.0.2 > > > This issue still occurs in several other dialogues on MAC OS X. > * Create Relational View Table -> Columns > * Create Relational View Procedure -> Result Set (+ I am able to edit values in row, without using "Edit" button) > * Create Relational Table -> Colums > * Create Relational Procedure -> Parameters, Result Set > * Create Relational Source Function -> Parameters > * Create Relational Native Query Procedure -> Parameters, Result Set > * Create Relational View -> Columns > * Changing translator in VDB Editor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2944) Remove the dynamic vdb terminology

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2944?page=com.atlassian.jira.plu... ] Steven Hawkins reassigned TEIIDDES-2944: ---------------------------------------- Description: We should remove/deprecate the dynamic term and instead reference native metadata import and ddl. (was: We should remove/deprecate the dynamic term and instead reference native metadata import and ddl - soon tooling will provide vdbs defined with ddl and the dynamic differentiation won't be needed.) Assignee: (was: Steven Hawkins) > Remove the dynamic vdb terminology > ---------------------------------- > > Key: TEIIDDES-2944 > URL: https://issues.jboss.org/browse/TEIIDDES-2944 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Documentation, Teiid Integration > Reporter: Steven Hawkins > > We should remove/deprecate the dynamic term and instead reference native metadata import and ddl. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2945) Issues with ddl generation

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-2945: ---------------------------------------- Summary: Issues with ddl generation Key: TEIIDDES-2945 URL: https://issues.jboss.org/browse/TEIIDDES-2945 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 10.1 Reporter: Steven Hawkins This can be separated out into separate issues if needed. - most ddl statements are not terminated with the semicolon delimiter. This was a mistake with the original grammar. We'll hopefully get this resolved with minimal breaking changes with TEIID-4528 - name in source and other options should be added by default. Is there a reason they are omitted by default? - triggers / update procedures don't seem to be emitted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2944) Remove the dynamic vdb terminology

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2944?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-4529 to TEIIDDES-2944: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-2944 (was: TEIID-4529) Component/s: Documentation Teiid Integration (was: Documentation) Fix Version/s: (was: 9.0) > Remove the dynamic vdb terminology > ---------------------------------- > > Key: TEIIDDES-2944 > URL: https://issues.jboss.org/browse/TEIIDDES-2944 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Documentation, Teiid Integration > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > We should remove/deprecate the dynamic term and instead reference native metadata import and ddl - soon tooling will provide vdbs defined with ddl and the dynamic differentiation won't be needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2925) Designer doesn't change java class name in the generated POJO module

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2925?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2925: --------------------------------------- regarding: But I see another problem. When I have already created JDG source tables and set materialization, I have the option to generated POJO again (Right click to viewTable which is materialized (viewAllBooks) and Modeling>Create POJO). But what I change the class name again. How is use case ? Teiid designer should be rename JDG source tables which are already set according to new class name or at least show warning that user has to rename this tables? The use case on creating a pojo (not thru materialization) could be for either for materialization or to use it when going to access JDG as a data source. So yes, we should probably add a warning so the user knows what they generated may not be usable in a current materialization unless the JDG source tables are regenerated. > Designer doesn't change java class name in the generated POJO module > -------------------------------------------------------------------- > > Key: TEIIDDES-2925 > URL: https://issues.jboss.org/browse/TEIIDDES-2925 > Project: Teiid Designer > Issue Type: Bug > Components: Build > Affects Versions: 10.0.2 > Environment: Fedora 24 > Reporter: Matej Kralik > Assignee: Barry LaFond > Fix For: 10.0.2 > > Attachments: screenshot1.png, screenshot2.png > > > I have a table (for example PersonMatView) and I want to create materialization. I set 'create POJO' and set java class name to Person (screenshot1). After that in the generated JDG module is Person.jar but in the jar, the class has name same like the table (Personmatview.class). (screenshot2). Is it required to have class name same as materialized table? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2925) Designer doesn't change java class name in the generated POJO module

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2925?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2925: --------------------------------------- Correct, the new JDG source tables should be created based on the class name. There's no technical reason they have to be the same as the view that was selected to be materialized. > Designer doesn't change java class name in the generated POJO module > -------------------------------------------------------------------- > > Key: TEIIDDES-2925 > URL: https://issues.jboss.org/browse/TEIIDDES-2925 > Project: Teiid Designer > Issue Type: Bug > Components: Build > Affects Versions: 10.0.2 > Environment: Fedora 24 > Reporter: Matej Kralik > Assignee: Barry LaFond > Fix For: 10.0.2 > > Attachments: screenshot1.png, screenshot2.png > > > I have a table (for example PersonMatView) and I want to create materialization. I set 'create POJO' and set java class name to Person (screenshot1). After that in the generated JDG module is Person.jar but in the jar, the class has name same like the table (Personmatview.class). (screenshot2). Is it required to have class name same as materialized table? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2943) Unhandled event loop exception adding child

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2943?page=com.atlassian.jira.plu... ] Steven Hawkins updated TEIIDDES-2943: ------------------------------------- Attachment: project.zip Exception: {code} java.lang.NullPointerException at org.eclipse.swt.widgets.TabFolder.gtk_switch_page(TabFolder.java:570) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2009) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4723) at org.eclipse.swt.internal.gtk.OS._gtk_widget_show(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_widget_show(OS.java:14774) at org.eclipse.swt.widgets.TabFolder.createItem(TabFolder.java:311) at org.eclipse.swt.widgets.TabItem.createWidget(TabItem.java:123) at org.eclipse.swt.widgets.TabItem.<init>(TabItem.java:75) at org.teiid.designer.transformation.ui.editors.ViewTableEditorPanel.createGeneralPropertiesTab(ViewTableEditorPanel.java:175) at org.teiid.designer.transformation.ui.editors.ViewTableEditorPanel.createPanel(ViewTableEditorPanel.java:162) at org.teiid.designer.relational.ui.edit.RelationalEditorPanel.<init>(RelationalEditorPanel.java:70) at org.teiid.designer.transformation.ui.editors.ViewTableEditorPanel.<init>(ViewTableEditorPanel.java:141) at org.teiid.designer.transformation.ui.editors.TransformationDialogModel.getEditorPanel(TransformationDialogModel.java:40) at org.teiid.designer.relational.ui.editor.EditRelationalObjectDialog.createDialogArea(EditRelationalObjectDialog.java:75) at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:161) at org.teiid.designer.relational.ui.editor.EditRelationalObjectDialog.createContents(EditRelationalObjectDialog.java:104) at org.eclipse.jface.window.Window.create(Window.java:430) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096) at org.eclipse.jface.window.Window.open(Window.java:792) at org.teiid.designer.transformation.ui.actions.CreateViewTableAction.run(CreateViewTableAction.java:171) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) 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) {code} > Unhandled event loop exception adding child > ------------------------------------------- > > Key: TEIIDDES-2943 > URL: https://issues.jboss.org/browse/TEIIDDES-2943 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 10.1 > Reporter: Steven Hawkins > Attachments: project.zip > > > Started with a new project / new model, tried to add a child to the view model and got an exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2943) Unhandled event loop exception adding child

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-2943: ---------------------------------------- Summary: Unhandled event loop exception adding child Key: TEIIDDES-2943 URL: https://issues.jboss.org/browse/TEIIDDES-2943 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 10.1 Reporter: Steven Hawkins Started with a new project / new model, tried to add a child to the view model and got an exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2742) Dataroles editor not updated when row filter added

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2742?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2742. ---------------------------------- > Dataroles editor not updated when row filter added > -------------------------------------------------- > > Key: TEIIDDES-2742 > URL: https://issues.jboss.org/browse/TEIIDDES-2742 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 9.0.4, 10.0.1 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.3 > Fix For: 10.0.2 > > > When adding Row Filter to a table, the list of filters is sometimes not updated. See Steps to reproduce for once such scenario. Closing the Data Role editor and reopening shows the correct row filters. > Also, in the Security column on the Model tab, the circle indicating a row filter is 'on' for the filter that does _not_ appear in the row filter list and is 'off' for the one that does. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2016