July 2010 - teiid-designer-issues

[JBoss JIRA] Closed: (TEIIDDES-62) Connector Binding Wizard - error checking and dialog display before screen is completed

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-62?page=com.atlassian.jira.plugin.... ] Barry LaFond closed TEIIDDES-62. -------------------------------- Assignee: Barry LaFond Resolution: Done Connection framework totally rewritten. Obsolete defect. > Connector Binding Wizard - error checking and dialog display before screen is completed > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-62 > URL: https://jira.jboss.org/browse/TEIIDDES-62 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 6.0.0 > Environment: Windows > Reporter: Warren Gibson > Assignee: Barry LaFond > Fix For: Future > > Attachments: screenshot-1.jpg > > > Connector Binding Wizard - It seems like the binding is being activated and error checking occurs before screen is completed and OK is selected. See attachment for many error dialogs being displayed at one time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-150) When exporting connectors, allow option to export as a CAF

by Paul Nittel (JIRA)

When exporting connectors, allow option to export as a CAF ---------------------------------------------------------- Key: TEIIDDES-150 URL: https://jira.jboss.org/jira/browse/TEIIDDES-150 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 6.0.0 Environment: fedora 10, Barry's 4/7/09 build Reporter: Paul Nittel Attachments: jbedsp-datadirect-0.0.1-SNAPSHOT.jar, ProductsXaConnector.cdk To test importing a connector, I exported one from an older Designer. In doing so, the Designer exports a .CDK file and whatever jar files the connector needs. These files are placed in the directory specified at the time of export. If we exported a Connector Archive File (CAF), all the pertinent files would be located in one easy-to-use package. -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-273) Importing different version of Yahoo Connector causes api.exception

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-273?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-273. ----------------------------------- Resolution: Won't Fix Connection framework totally rewritten. Obsolete defect. > Importing different version of Yahoo Connector causes api.exception > ------------------------------------------------------------------- > > Key: TEIIDDES-273 > URL: https://jira.jboss.org/browse/TEIIDDES-273 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Environment: Windows > Reporter: Warren Gibson > Assignee: Barry LaFond > > Had a yahoo connector in Designer and tried to import a different version of yahoo connector and received the following error. To get around the problem I had to delete the existing yahoo connector, shut down designer, restart designer, and import the new version of yahoo connector. > com.metamatrix.admin.api.exception.AdminComponentException: Delete of Connector type "Yahoo Connector" failed. Currently in > use by a Connector Binding. > at > com.metamatrix.dqp.embedded.services.EmbeddedConfigurationService.deleteConnectorType(EmbeddedConfigurationService.java:917 > ) > at com.metamatrix.dqp.embedded.admin.DQPConfigAdminImpl.deleteConnectorType(DQPConfigAdminImpl.java:231) > 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 com.metamatrix.jdbc.EmbeddedConnection$1.invoke(EmbeddedConnection.java:121) > at $Proxy12.deleteConnectorType(Unknown Source) > at com.metamatrix.modeler.dqp.ui.workspace.WorkspaceExecutor.removeConnectorType(WorkspaceExecutor.java:325) > at > com.metamatrix.modeler.dqp.ui.workspace.WorkspaceExecutor$BindingListener.handleConnectorTypeEvent(WorkspaceExecutor.java:5 > 17) > at com.metamatrix.modeler.dqp.ui.workspace.WorkspaceExecutor$BindingListener.stateChanged(WorkspaceExecutor.java:492) > at com.metamatrix.modeler.dqp.internal.config.ConfigurationManagerImpl.fireChangeEvent(ConfigurationManagerImpl.java:478) > at com.metamatrix.modeler.dqp.internal.config.ConfigurationManagerImpl.saveConfigLocal(ConfigurationManagerImpl.java:151) > at > com.metamatrix.modeler.dqp.internal.config.ConfigurationManagerImpl.removeConnectorType(ConfigurationManagerImpl.java:321) > at > com.metamatrix.modeler.internal.dqp.ui.workspace.actions.DeleteConnectorTypeAction.run(DeleteConnectorTypeAction.java:72) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) > 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:386) > 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:549) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) > at org.eclipse.equinox.launcher.Main.run(Main.java:1236) > at org.eclipse.equinox.launcher.Main.main(Main.java:1212) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-337) Cut and paste from SQL Explorer enters VDBName as Model name in the xmi file, but valids in transformation

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-337?page=com.atlassian.jira.plugin... ] Barry LaFond closed TEIIDDES-337. --------------------------------- Assignee: Barry LaFond Resolution: Won't Fix VDB Editor, VDB content have totally changed. SQL Explorer replaced with standard DTP querying. Obsolete defect. > Cut and paste from SQL Explorer enters VDBName as Model name in the xmi file, but valids in transformation > ---------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-337 > URL: https://jira.jboss.org/browse/TEIIDDES-337 > Project: Teiid Designer > Issue Type: Bug > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: Future > > Attachments: 365698.zip > > > Using my attached Model Project Set (365698.zip)(Issue tracker ticket) Execute the NewVDB.VDB in the Designer, right click on DateTZ_Oracle.DATETZ.TABLE2 table and "Generate Select in SQL Editor": > select ROW_ID, TZ_USED, TS_STRING, DATEVAL, TS_VAL, TS_W_TZ_VAL, TS_W_LTZ_VAL from "NewVDB"."DateTZ_Oracle.DATETZ.TABLE2" > Return to the Designer Perspective and create a new Base Table under the VModel, paste the the clipboard contents from the SQL Editor into the Transformation Editor, click "Save/Validate SQL". You'll notice the validator removes the "NewVDB" name and the quotes and validates and saves the transformation: > SELECT ROW_ID, TZ_USED, TS_STRING, DATEVAL, TS_VAL, TS_W_TZ_VAL, TS_W_LTZ_VAL > FROM DateTZ_Oracle.DATETZ.TABLE2 > Now Save, Build and Synchronize the NewVDB.VDB. Execute again and query the new View table. You'll receive a "Group does not exist: NewVDB.TABLE2" error. The xmi file contains the VDB name as the model name in the transformation. > But apparently, if you go back into the transformation and make any changes and save/validate again it corrects the issue. (Turned SQL Optimization off, saved, Turned it back on, saved) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-222) Hide "Connector Types" by default in Connector window

by Ramesh Reddy (JIRA)

Hide "Connector Types" by default in Connector window ----------------------------------------------------- Key: TEIIDDES-222 URL: https://jira.jboss.org/jira/browse/TEIIDDES-222 Project: Teiid Designer Issue Type: Task Components: VDB & Execution Affects Versions: 6.1.0 Reporter: Ramesh Reddy When user creates a Connector binding manually or one created automatically due to the import process, the created binding will not readily visible in the "Connectors" window, thus confuses the user. in rder to find the newly created "Connector", they need to scroll down or "hide connector types" before it can be found. It would be better the "Connector Types" are hidden by default, as they do not provide any real information by being visible. They are only required by the user during the creation of the "Connector" where they are shown anyway. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-224) The ConfigurationInfo.def file has verbose settings for the ComponentTypes

by Ramesh Reddy (JIRA)

The ConfigurationInfo.def file has verbose settings for the ComponentTypes -------------------------------------------------------------------------- Key: TEIIDDES-224 URL: https://jira.jboss.org/jira/browse/TEIIDDES-224 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 6.1.0 Reporter: Ramesh Reddy Fix For: 6.2.0 Currently when VDB is written, the <ComponentTypes> section in the ConfigurationInfo.def file defines the component types for all the bindings defined. However the number of properties defined for each component type include all the properties in hierarchy of that Component Type. Which verbose and confusing. For example in Configuration.XML file a "Oracle Connector" defined with it's hierarchy as Oracle Connector --> JDBC Connector --> Connector where Teiid defines properties at each level, but when the def file these properties are flattened and all properties are written under component type "Oracle Connector". Looking at the issue, "ComponentType" fragment of the XML is optional, if the connector type is already in the "configuration.xml". However, designer still need to write the ComponentType information for custom connector types as that information will not be in the configuration.xml file. To determine, if a connector type is already in the "configuration.xml", the designer can check a property called "standard", if the value is "true" it can safely ignore adding the component type to the .def file. Teiid will supply the configuration.xml file with "standard" property set on all the built in types. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-243) Request to have Root cause of connector error in designer SQL Explorer dialog instead of 'CapabilitiesMessage'

by Debbie Steigner (JIRA)

Request to have Root cause of connector error in designer SQL Explorer dialog instead of 'CapabilitiesMessage' -------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-243 URL: https://jira.jboss.org/jira/browse/TEIIDDES-243 Project: Teiid Designer Issue Type: Feature Request Reporter: Debbie Steigner Fix For: 6.1.0 In the designer, when a connector can't start and throws an exception, it pops up a dialog that says: "Unable to create a connection for request com.metamatrix.dqp.message.CapabilitiesMessage@1cee695" However, this is not the root cause exception, so every time it happens, one must find the exception in the log and find the root cause. The root cause is often something to do with bad credentials, or an expired password, or the like. Not having this is really irritating and needlessly time-consuming. So, the feature request is to drill down in the exception stack trace to the root cause and report it's message in the dialog. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-218) A VDB with a materialized view model is created with errors

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-218?page=com.atlassian.jira.plugin... ] Barry LaFond closed TEIIDDES-218. --------------------------------- Assignee: Barry LaFond Resolution: Won't Fix VDB Editor framework has been totally replaced. Materialized Views are now first-class Physical models, same as any other. Obsolete defect. > A VDB with a materialized view model is created with errors > ----------------------------------------------------------- > > Key: TEIIDDES-218 > URL: https://jira.jboss.org/browse/TEIIDDES-218 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 6.2.0 > Environment: Fedora 10, JDK 1.6 Teiid Designer circa early July > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: Future > > > I'm in the process of recreating the Customer projects, one of which uses Materialized Views (which aren't yet available in Teiid). The VDB validation routines are generating errors in the VDB, so it cannot be used. The errors are not shown in the log file, just the VDB's Problems tab. An example of the errors are: > Error creating truncate scripts for VDB <name of the VDB> > Error creating swap scripts for VDB <name of the VDB> > Whether the Designer should expose this property or the validation should produce a warning instead of an error is up to you guys. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-223) Loaded Connectors dialog is empty

by Ramesh Reddy (JIRA)

Loaded Connectors dialog is empty --------------------------------- Key: TEIIDDES-223 URL: https://jira.jboss.org/jira/browse/TEIIDDES-223 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.2.0 Reporter: Ramesh Reddy I then defined my connector and dragged my model into it. That part > seems to be fine. > > Just when I go to my VDB definition, on the "Execute" page, I need to > assign a connector in order for my VDB to be able to execute. > > But I just cannot select my pre-defined connector there as the "Loaded > Connectors" tab is empty. I can define a new connector there, using the > same properties as my existing connector, but just using a different > name, and it will work fine. Loaded Bindings must have shown my previous binding to select from. -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-200) Source Model Not Added To VDB Execution Page Of VDB Editor

by Dan Florian (JIRA)

Source Model Not Added To VDB Execution Page Of VDB Editor ---------------------------------------------------------- Key: TEIIDDES-200 URL: https://jira.jboss.org/jira/browse/TEIIDDES-200 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.1.0 Environment: Ubuntu 8.04 Reporter: Dan Florian Fix For: Future Attachments: BookSetMixed.zip Add BooksDoc to the VDB then go to the Execution tab. This shows in the log: Unable to resolve reference to a resource with the URI file:/home/dflorian/Runtime-Workspaces/.metadata/.plugins/org.teiid.designer.vdb.edit/vdbWorkingFolder/1243886654886_6290397909764948307/Book%20Set%20Mixed/BookDatatypes.xsd Notice that Books.xmi is NOT added but BooksSS.xmi is added. If you add Books.xmi by itself it DOES getting added OK. Added model project set as an attachment. -- 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, 5 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2010