April 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1118: ----------------------------------- Fix Version/s: 7.7.1 (was: 7.7) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=781036 (was: https://bugzilla.redhat.com/show_bug.cgi?id=781036) > Add/Remove operations on a VDB should block other operations on the VDB > ----------------------------------------------------------------------- > > Key: TEIIDDES-1118 > URL: https://issues.jboss.org/browse/TEIIDDES-1118 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Marc Shirley > Assignee: Mark Drilling > Fix For: 7.7.1 > > > As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception: > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435) > at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244) > at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709) > at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) > at org.eclipse.equinox.launcher.Main.run(Main.java:1408) > at org.eclipse.equinox.launcher.Main.main(Main.java:1384) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] Barry LaFond reopened TEIIDDES-1118: ------------------------------------ The fix broke on linux and we double-encoding the URI causing same ArrayIndexOutOfBoundsException. Re-opening > Add/Remove operations on a VDB should block other operations on the VDB > ----------------------------------------------------------------------- > > Key: TEIIDDES-1118 > URL: https://issues.jboss.org/browse/TEIIDDES-1118 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Marc Shirley > Assignee: Mark Drilling > Fix For: 7.7.1 > > > As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception: > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435) > at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244) > at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709) > at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) > at org.eclipse.equinox.launcher.Main.run(Main.java:1408) > at org.eclipse.equinox.launcher.Main.main(Main.java:1384) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-226) Problem importing Synonyms into VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-226?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-226: ---------------------------------- Assignee: Mark Drilling > Problem importing Synonyms into VDB > ----------------------------------- > > Key: TEIIDDES-226 > URL: https://issues.jboss.org/browse/TEIIDDES-226 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration, VDB & Execution > Affects Versions: 6.0.0, 6.1.0, 6.2.0 > Reporter: Ram Yelamanchilli > Assignee: Mark Drilling > Priority: Minor > Labels: Designer, SYNONYM, VDB > Fix For: 8.0 > > > I'm trying to import synonyms When I create a source model importing SYNONYM, source model is created with the following error. > "The Base Table must reference one more more columns; there are none." > Designer version is 6.2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-175) Define a contract beween Teiid and Designer that enables Designer to use different versions of Teiid.

by John Doyle (JIRA)

Define a contract beween Teiid and Designer that enables Designer to use different versions of Teiid. ----------------------------------------------------------------------------------------------------- Key: TEIIDDES-175 URL: https://jira.jboss.org/jira/browse/TEIIDDES-175 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Reporter: John Doyle Teiid Designer should be able to execute models/VDBs with different versions of Teiid. In order to accomplish this in a user friendly manner, a contract should be agreed upon between Teiid and Designer. Designer could invoke Teiid via this contract and the user would be able to easily repoint Designer to different versions of Teiid in order to test models/VDBs across different versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-173) In-line rename not enabled for newly created Web Service Operation

by Barry LaFond (JIRA)

In-line rename not enabled for newly created Web Service Operation ------------------------------------------------------------------ Key: TEIIDDES-173 URL: https://jira.jboss.org/jira/browse/TEIIDDES-173 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Priority: Minor Fix For: Future 1) Open Web Service Model in Model Editor 2) Select Web Service Interface in Model explorer 3) Right-click select New > Child > Operation 4) New Operation shows up in Explorer, but auto-rename is not enabled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
3
0 / 0

[JBoss JIRA] (TEIIDDES-157) Designer Performance issues with Large Models

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-157?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-157. ----------------------------------- Resolution: Won't Fix Outdated. > Designer Performance issues with Large Models > --------------------------------------------- > > Key: TEIIDDES-157 > URL: https://issues.jboss.org/browse/TEIIDDES-157 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 6.0.0 > Environment: Windows or LINUX > Reporter: Barry LaFond > Fix For: Future > > > Tested modeling very large relational models and quickly ran into performance issues in Designer. > With Heap size set to 512K I could really only work with models < 30MB in size. Bumping the heap size to 1024K allowed creation of 72MB model. This equates to ~400,000 columns. I was also able to Clone the project and create a second 72MB model. However any kind of editing became unbearable as soon as I maxed out on Memory usage ~ Heap size. > Finished testing by closing both projects (145MB of models) and it took a couple of hours to close. > Bottom line is there is a practical limit to how large your model/project set can be before modeling becomes an unbearable task. > We need to fix this, but I'm afraid it won't come until DNA comes online so we don't have to load all model objects (and their properties) in memory. > In the meantime, we should warn users (i.e. Know issue). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-116) Add ability to perform partial copy model operations in new model wizard

by Barry LaFond (JIRA)

Add ability to perform partial copy model operations in new model wizard ------------------------------------------------------------------------ Key: TEIIDDES-116 URL: https://jira.jboss.org/jira/browse/TEIIDDES-116 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: 6.1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-113) Ability to create partial copy of a model with new model wizard

by Barry LaFond (JIRA)

Ability to create partial copy of a model with new model wizard --------------------------------------------------------------- Key: TEIIDDES-113 URL: https://jira.jboss.org/jira/browse/TEIIDDES-113 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.0 Reporter: Barry LaFond Need to be able to create a new model from existing model (copy) and weed-out unwanted model children. Designer 5.5.3 version contained this feature, but after further review, the design was incomplete and has resulted in multiple bugs. So, plan is to remove this feature for the 6.0.0 release and then re-design & implement for 6.1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
4
0 / 0

[JBoss JIRA] (TEIIDDES-109) Feature Request to add Model Project Templates

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-109?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-109: ------------------------------------- Assignee: Mark Drilling (was: Barry LaFond) > Feature Request to add Model Project Templates > ---------------------------------------------- > > Key: TEIIDDES-109 > URL: https://issues.jboss.org/browse/TEIIDDES-109 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration > Affects Versions: 6.0.0 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: 8.0 > > > Please submit the creation and use of template projects as a feature. Template projects should work similiar to how templates work in IDE's. From Issue Tracker ticket https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-109) Feature Request to add Model Project Templates

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-109?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-109: ---------------------------------- Fix Version/s: 8.0 (was: No Future) > Feature Request to add Model Project Templates > ---------------------------------------------- > > Key: TEIIDDES-109 > URL: https://issues.jboss.org/browse/TEIIDDES-109 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration > Affects Versions: 6.0.0 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: 8.0 > > > Please submit the creation and use of template projects as a feature. Template projects should work similiar to how templates work in IDE's. From Issue Tracker ticket https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

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 April 2012