January 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1010: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=780725 > Indexes are not qualified when imported with Teiid Designer > ----------------------------------------------------------- > > Key: TEIIDDES-1010 > URL: https://issues.jboss.org/browse/TEIIDDES-1010 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.0 > > > Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1010: ---------------------------------------------- Bugzilla Update: Perform > Indexes are not qualified when imported with Teiid Designer > ----------------------------------------------------------- > > Key: TEIIDDES-1010 > URL: https://issues.jboss.org/browse/TEIIDDES-1010 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.0 > > > Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1220) SQLStringVisitor should create call visitNode on Select

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-1220: ---------------------------------------- Summary: SQLStringVisitor should create call visitNode on Select Key: TEIIDDES-1220 URL: https://issues.jboss.org/browse/TEIIDDES-1220 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.6 Environment: Fedora 16, JBDS 5.0.0 M5, Teiid Designer 7.6 Reporter: Paul Nittel Fix For: 7.7 Here's what I get: eclipse.buildId=unknown java.version=1.6.0_22 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product com.jboss.jbds.product.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.jbds.product.product Error Wed Jan 18 16:35:12 CST 2012 Unhandled event loop exception java.lang.NullPointerException at com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent.expandSelect(QueryDisplayComponent.java:586) at com.metamatrix.modeler.transformation.ui.editors.sqleditor.SqlEditorPanel.expandCurrentSelect(SqlEditorPanel.java:1872) at com.metamatrix.modeler.transformation.ui.editors.sqleditor.SqlEditorPanelWrapper.expandCurrentSelect(SqlEditorPanelWrapper.java:161) at com.metamatrix.modeler.transformation.ui.editors.sqleditor.actions.ExpandSelect.doRun(ExpandSelect.java:48) at com.metamatrix.ui.actions.AbstractAction$1.run(AbstractAction.java:537) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at com.metamatrix.ui.actions.AbstractAction.run(AbstractAction.java:540) 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:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1182) MED Boolean Property Definitions Should Not Store Allowed Values In The MED

by Dan Florian (Created) (JIRA)

MED Boolean Property Definitions Should Not Store Allowed Values In The MED --------------------------------------------------------------------------- Key: TEIIDDES-1182 URL: https://issues.jboss.org/browse/TEIIDDES-1182 Project: Teiid Designer Issue Type: Task Components: Editors Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.7 Created a boolean property definition in a MED and noticed the allowed values of "true" and "false" got stored with the property definition. For boolean values the allowed values need not be stored in the MED. This used to not work like this. -- 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

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1165) MED Editor Properties page should utilize same "Model Class" and "Model Type" combo boxes as the New Metadata Model wizard.

by Barry LaFond (Created) (JIRA)

MED Editor Properties page should utilize same "Model Class" and "Model Type" combo boxes as the New Metadata Model wizard. --------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1165 URL: https://issues.jboss.org/browse/TEIIDDES-1165 Project: Teiid Designer Issue Type: Enhancement Reporter: Barry LaFond Assignee: Dan Florian The properties tab currently presents a metamodel URI combo box, but we've been trying to get away from EMF. The New Model wizard displays only the simple Model Class and Model Type values. We'd of course, limit the Model Classes to Relational, XML Document, Web Services and Function models. Model types would be Source, View and in the case of Function model, "User Defined Function" model type. Without the Model Type selection, which is currently missing, users won't be able to target or limit applying properties to specific model types. The REST extension properties, for instance is only applicable to "View" models. It's MED should include supported Model Types list to include only View + Relational. We probably need to allow a third Relational model type of "BOTH", so an MED wouldn't have to be created for both metamodels? -- 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

12 years, 11 months

4
5
0 / 0

[JBoss JIRA] (TEIIDDES-1210) MED Schema Should Enforce Unique Extend Metaclass And Unique Property Definition IDs Within A Metaclass

by Dan Florian (Created) (JIRA)

MED Schema Should Enforce Unique Extend Metaclass And Unique Property Definition IDs Within A Metaclass ------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1210 URL: https://issues.jboss.org/browse/TEIIDDES-1210 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.7 The current MED schema does not produce a parsing error when duplicate metaclasses and duplicate property identifiers within a metaclass are found. The MED schema should enforce that there are no duplicate metaclasses and no duplicate property identifiers within a metaclass. -- 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

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1187) Add MED Editor's Overview info as a second page in the New MED wizard

by Barry LaFond (Created) (JIRA)

Add MED Editor's Overview info as a second page in the New MED wizard --------------------------------------------------------------------- Key: TEIIDDES-1187 URL: https://issues.jboss.org/browse/TEIIDDES-1187 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Reporter: Barry LaFond Fix For: 7.7 While adding docs to 7.6 MED framework, and working with the "New" wizard, it seems that we could add a second page which included the Namespace URI, extended Model type, Description, etc. Creating an Empty MED is really no different than the "New > File" wizard. Let's add another page and put some meat in this thing. -- 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

12 years, 11 months

5
6
0 / 0

[JBoss JIRA] (TEIIDDES-1212) Fully Qualified Names in Source doesn't work on JDBC Import

by Debbie Steigner (JIRA)

Debbie Steigner created TEIIDDES-1212: ----------------------------------------- Summary: Fully Qualified Names in Source doesn't work on JDBC Import Key: TEIIDDES-1212 URL: https://issues.jboss.org/browse/TEIIDDES-1212 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4.2 Reporter: Debbie Steigner Priority: Critical Fix For: 7.4.2 Marking the Fully Qualified Source Names on a JDBC Import into Teiid Designer does not create the correct "Name in Source" property on the tables. It makes them the tablename only not schema.tablename. This functionality did work in 7.1.1 but no longer works in 7.4.x, this is a major issue, most customers do not have the user who is the owner of the schema they are importing, so they must use fully qualified names to source. If the import doesn't properly add the name in source then the customer has to manually make this change for every table. -- 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

12 years, 11 months

2
2
0 / 0

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

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1118. ------------------------------------- Resolution: Done Modified VdbModelEntry.synchronizeModelEntry method to use the eclipse URIUtil method to get the URI. According to http://wiki.eclipse.org/Eclipse/UNC_Paths , the java utils can sometimes be a little flaky when dealing with UNC paths. Retested ok after the change. > 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 > > > 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1060) Incorrect Transformation when using 'Create XML to Scalar Transformation' in Teiid Designer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1060?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1060: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=780888 (was: https://bugzilla.redhat.com/show_bug.cgi?id=780888) > Incorrect Transformation when using 'Create XML to Scalar Transformation' in Teiid Designer > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1060 > URL: https://issues.jboss.org/browse/TEIIDDES-1060 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Ted Jones > Fix For: 7.7, 7.7.1 > > > Incorrect Transformation when using 'Create XML to Scalar Transformation' in Teiid Designer. See Steps to reproduce section for full description. -- 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

12 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2012