August 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-464) Teiid 7.0 XML integration issues

by Steve Hawkins (JIRA)

Teiid 7.0 XML integration issues -------------------------------- Key: TEIIDDES-464 URL: https://jira.jboss.org/browse/TEIIDDES-464 Project: Teiid Designer Issue Type: Quality Risk Components: Import/Export, Modeling, Teiid Integration Affects Versions: 7.0 Reporter: Steve Hawkins Priority: Critical With Teiid 7.0 there are several changes that affect functionality provided in the designer: 1. The xml imports (relational or source) are now invalid. There is now engine functionality to handle row extraction. If possible these importers should be retargeted. 2. The xquery web services model is now invalid. XQuery is now executed through the XMLQUERY expression, so the command type is just regular SQL - not XQuery. -- 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

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-536) JDBC importer should offer to widen unsigned types

by Steve Hawkins (JIRA)

JDBC importer should offer to widen unsigned types -------------------------------------------------- Key: TEIIDDES-536 URL: https://jira.jboss.org/browse/TEIIDDES-536 Project: Teiid Designer Issue Type: Quality Risk Components: Import/Export Affects Versions: 7.1 Reporter: Steve Hawkins Some databases support unsigned types (mysql) and others such as Sybase/SQLServer have types, tinyint, that are unsigned and do not map naturally to the corresponding signed teiid type. The importer should offer to widen theses types, e.g. tinyint becomes a short instead of a byte. -- 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

13 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-521) Add "importer" or model template for file translator

by Steve Hawkins (JIRA)

Add "importer" or model template for file translator ---------------------------------------------------- Key: TEIIDDES-521 URL: https://jira.jboss.org/browse/TEIIDDES-521 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.0 Reporter: Steve Hawkins Most commonly to use the TEXTTABLE table function (the replacement for the text connector) the user will need to use a File Translator/File Resource Adapter. Since the file translator only exposes a known set of procedures, this could be as simple as a model copy. The other approach would be to use the translator api to get the metadata from the translator and then turn that into a model. This is also needed for the WS Translator/WS resource adapter. See TEIIDDES-464 -- 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

13 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-471) Turn on Nightly Tests

by John Verhaeg (JIRA)

Turn on Nightly Tests --------------------- Key: TEIIDDES-471 URL: https://jira.jboss.org/browse/TEIIDDES-471 Project: Teiid Designer Issue Type: Task Components: Housekeeping Affects Versions: 6.3 Reporter: John Verhaeg Fix For: 7.0 We have enough new tests now that we can depend on going forward, so at least some test projects need to be built and run each night. -- 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

13 years, 3 months

5
12
0 / 0

[JBoss JIRA] Created: (TEIIDDES-214) Validate that the jdbc4olap driver works as expected in Designer and Teiid.

by John Doyle (JIRA)

Validate that the jdbc4olap driver works as expected in Designer and Teiid. --------------------------------------------------------------------------- Key: TEIIDDES-214 URL: https://jira.jboss.org/jira/browse/TEIIDDES-214 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: John Doyle Assignee: John Doyle http://www.jdbc4olap.org/ provides a type 4 JDBC driver for OLAP sources that support XMLA. Supporting this driver will provide access to many OLAP sources (SAP, Microsoft, Mondrian) Currently the only OLAP source that we have tested with is SAP BW via the OLAP BAPI interface. Those BAPIs are procedural and require the model designer to create extensive procedural logic in their models. jdbc4olap should enable a user to access OLAP data via standard JDBC semantics. -- 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

13 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-503) Update Designer embedded help to reflect 7.0 changes

by Barry LaFond (JIRA)

Update Designer embedded help to reflect 7.0 changes ---------------------------------------------------- Key: TEIIDDES-503 URL: https://jira.jboss.org/browse/TEIIDDES-503 Project: Teiid Designer Issue Type: Task Affects Versions: 7.0, 7.1 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.1 Changes to the VDB editor, Connections (JCA & DTP) and the adoption of the new "Teiid in AS" concept requires updating Designer's embedded help. -- 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

13 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-403) Eliminate use of restricted Eclipse classes

by Barry LaFond (JIRA)

Eliminate use of restricted Eclipse classes ------------------------------------------- Key: TEIIDDES-403 URL: https://jira.jboss.org/jira/browse/TEIIDDES-403 Project: Teiid Designer Issue Type: Sub-task Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Designer still uses some restricted Eclipse classes. Goal is to become compliant with the restrictions. -- 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

13 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-510) Remove old Designer Preferences Import & Export buttons and underlying functions

by Paul Nittel (JIRA)

Remove old Designer Preferences Import & Export buttons and underlying functions -------------------------------------------------------------------------------- Key: TEIIDDES-510 URL: https://jira.jboss.org/browse/TEIIDDES-510 Project: Teiid Designer Issue Type: Task Affects Versions: 7.0 Environment: All Reporter: Paul Nittel I noticed the Preferences Designer Import and Export functions both use the Import file chooser. Barry pointed out the correct methods are to use File > Import (or Export) > General > Preferences. Please remove all references to the older, obsolete, and, now incorrect, version. -- 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

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-519) Delete project - Unhandled event loop exception and project not deleted

by Warren Gibson (JIRA)

Delete project - Unhandled event loop exception and project not deleted ----------------------------------------------------------------------- Key: TEIIDDES-519 URL: https://jira.jboss.org/browse/TEIIDDES-519 Project: Teiid Designer Issue Type: Bug Components: Housekeeping Affects Versions: 7.0 Reporter: Warren Gibson Running Teiid Designer in JBoss Developer Studio Imported BQT_ORCL9 project attached. Did some editing Decided to delete the project. Selected the project in the Model Expl tree with right mouse. Selected delete. Got a dialog wanting me to confirm the delete. Selected Yes for the delete. Project was not get deleted from tree. Refreshed the tree and project still exists. Notice an Unhandled event loop exception: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:3884) at org.eclipse.swt.SWT.error(SWT.java:3799) at org.eclipse.swt.SWT.error(SWT.java:3770) at org.eclipse.swt.widgets.Widget.error(Widget.java:450) at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:532) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:155) at org.eclipse.ltk.internal.ui.refactoring.actions.DeleteResourcesHandler.execute(DeleteResourcesHandler.java:40) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommandInContext(HandlerService.java:270) at org.eclipse.ui.internal.ide.actions.LTKLauncher.runCommand(LTKLauncher.java:95) at org.eclipse.ui.internal.ide.actions.LTKLauncher.openDeleteWizard(LTKLauncher.java:47) at org.eclipse.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:481) at com.metamatrix.modeler.internal.ui.actions.DeleteResourceAction.doRun(DeleteResourceAction.java:386) 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$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) 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:194) 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:368) 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:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- 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

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-550) Import DDL to Relational Table misses columns for primary, foreign keys

by Paul Nittel (JIRA)

Import DDL to Relational Table misses columns for primary, foreign keys ----------------------------------------------------------------------- Key: TEIIDDES-550 URL: https://jira.jboss.org/browse/TEIIDDES-550 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, TeiidDesigner 7.1 M1 Reporter: Paul Nittel Attachments: motels.ddl I imported the motels.ddl example file to populate the foo model. When finished importing, I had a number of errors where the importer had created primary and foreign keys without specifying columns for those keys. In one case, here's the DDL: CREATE TABLE CustomerFamilyHistory ( customerfamilyhistoryid number(10) CONSTRAINT customerfamilyhistoryid_pk PRIMARY KEY, firstname varchar2(50) NOT NULL, lastname varchar2(50) NOT NULL, age number(3), sibling varchar2(20), customerid number(7) NOT NULL ); The primary key, customerfamilyhistoryid_pk, is created, but no reference to customerfamilyhistoryid is provided. -- 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

13 years, 6 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2010