February 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1242) Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1242?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1242: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=781176 (was: https://bugzilla.redhat.com/show_bug.cgi?id=781176) > Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882 > ----------------------------------------------------------------- > > Key: TEIIDDES-1242 > URL: https://issues.jboss.org/browse/TEIIDDES-1242 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Critical > Fix For: 7.7 > > > The Handshake and LogonResult classes are not properly accounting for backwards compatibility. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1242) Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1242?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1242: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 781176|https://bugzilla.redhat.com/show_bug.cgi?id=781176] from ON_QA to MODIFIED > Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882 > ----------------------------------------------------------------- > > Key: TEIIDDES-1242 > URL: https://issues.jboss.org/browse/TEIIDDES-1242 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Critical > Fix For: 7.7 > > > The Handshake and LogonResult classes are not properly accounting for backwards compatibility. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1242) Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1242?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1242: ---------------------------------- Priority: Critical (was: Major) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=781176 (was: https://bugzilla.redhat.com/show_bug.cgi?id=781176) Assignee: Barry LaFond (was: Steven Hawkins) > Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882 > ----------------------------------------------------------------- > > Key: TEIIDDES-1242 > URL: https://issues.jboss.org/browse/TEIIDDES-1242 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Critical > Fix For: 7.7 > > > The Handshake and LogonResult classes are not properly accounting for backwards compatibility. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1242) Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1242?page=com.atlassian.jira.plu... ] Van Halbert moved TEIID-1930 to TEIIDDES-1242: ---------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-1242 (was: TEIID-1930) Affects Version/s: 7.6 (was: 7.6) Component/s: Teiid Integration (was: JDBC Driver) Fix Version/s: 7.7 (was: 8.0) (was: 7.7) > Designer needs to upgrade to Teiid 7.7.x client to fix TEIID-1882 > ----------------------------------------------------------------- > > Key: TEIIDDES-1242 > URL: https://issues.jboss.org/browse/TEIIDDES-1242 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.7 > > > The Handshake and LogonResult classes are not properly accounting for backwards compatibility. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-305) Create an importer for the LDAP Connector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-305?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated TEIIDDES-305: --------------------------------------------- Bugzilla Update: Perform > Create an importer for the LDAP Connector > ----------------------------------------- > > Key: TEIIDDES-305 > URL: https://issues.jboss.org/browse/TEIIDDES-305 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: Future > Reporter: Michael Walker > > Designer should be able to import LDAP metadata and auto-generate a relational model. This would remove the manual effort of creating models, which is error-prone. > The importer should support the ability to gather cost statistics, as it greatly enhances overall query performance, and is always recommended for use with LDAP data source connections. > The importer could also create normalized tables to represent multi-valued attributes of a given DN. See linked issue for more info on this request. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-305) Create an importer for the LDAP Connector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-305?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated TEIIDDES-305: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=780846 > Create an importer for the LDAP Connector > ----------------------------------------- > > Key: TEIIDDES-305 > URL: https://issues.jboss.org/browse/TEIIDDES-305 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: Future > Reporter: Michael Walker > > Designer should be able to import LDAP metadata and auto-generate a relational model. This would remove the manual effort of creating models, which is error-prone. > The importer should support the ability to gather cost statistics, as it greatly enhances overall query performance, and is always recommended for use with LDAP data source connections. > The importer could also create normalized tables to represent multi-valued attributes of a given DN. See linked issue for more info on this request. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1043) Test Connection on LDAP Connection Profile Wizard page does not enable

by Barry LaFond (JIRA)

Test Connection on LDAP Connection Profile Wizard page does not enable ---------------------------------------------------------------------- Key: TEIIDDES-1043 URL: https://issues.jboss.org/browse/TEIIDDES-1043 Project: Teiid Designer Issue Type: Bug Components: Datatools Integration Affects Versions: 7.4, 7.5, 7.4.2 Reporter: Barry LaFond Fix For: 7.6 Filling in required info in new LDAP connection profile does not enable the "Test Connection" button. Looks like a "setPingButtonEnabled(true);" call needs to be made at the end of the LdapProfileDetailsWizardPage.validate() method, but adding the code ends up throwing an NPE when pressed. So, it looks like there is no IConnectionFactoryProvider/IConnectionFactory contributed for the LDAP connection to use to "ping" the DB. This would have to be completed in order for the Test Connection button to not throw an NPE -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
6
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 commented on TEIIDDES-1010: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> made a comment on [bug 780725|https://bugzilla.redhat.com/show_bug.cgi?id=780725] Retargeted to SOA 6 because Teiid Designer has indicated thats when this will be fixed. > 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

14 years, 2 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 commented on TEIIDDES-1010: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 780725|https://bugzilla.redhat.com/show_bug.cgi?id=780725] from NEW to ASSIGNED > 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

14 years, 2 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1118: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> made a comment on [bug 781036|https://bugzilla.redhat.com/show_bug.cgi?id=781036] Designer committed the fix to its 7.7 branch and should be in the SOA 5.3 release. > 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

14 years, 2 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 February 2012