July 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-425) Add query capabilities to the Import from JDBC in the Designer

by Debbie Steigner (JIRA)

Add query capabilities to the Import from JDBC in the Designer -------------------------------------------------------------- Key: TEIIDDES-425 URL: https://jira.jboss.org/jira/browse/TEIIDDES-425 Project: Teiid Designer Issue Type: Feature Request Reporter: Debbie Steigner Fix For: 7.0 For dealing with databases with extrremely large numbers of tables 10,000 +, it would be very helpful to have these 2 features: 1. Search / Filter capabilities 2. Ability to turn off the tables details on the "right" side of the dialog as retrieving that data table by table is exceedingly slow especially when dealing with 1000's of tables. -- 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

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-472) Support multi-source bindings

by John Verhaeg (JIRA)

Support multi-source bindings ----------------------------- Key: TEIIDDES-472 URL: https://jira.jboss.org/browse/TEIIDDES-472 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.3 Reporter: John Verhaeg Fix For: 7.1 Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation. The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names. -- 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

15 years, 9 months

2
1
0 / 0

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

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-226?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-226: ---------------------------------- Fix Version/s: 7.2 (was: 7.1) > Problem importing Synonyms into VDB > ----------------------------------- > > Key: TEIIDDES-226 > URL: https://jira.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 > Fix For: 7.2 > > > 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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-215) Autoincrement incorrectly imported for SQL Server 2008

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-215?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-215: ---------------------------------- Fix Version/s: 7.2 (was: 7.1) > Autoincrement incorrectly imported for SQL Server 2008 > ------------------------------------------------------ > > Key: TEIIDDES-215 > URL: https://jira.jboss.org/browse/TEIIDDES-215 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.1.0 > Environment: Windows XP, Eclipse 3.4.2, SQL Server 2008, JDBC driver by Microsoft > Reporter: Michael Riedmueller > Fix For: 7.2 > > > Table attributes with type int and autoincrement set to true are imported with data type "int identity", autoincrement is NOT set in the properties. > This should be data type "int" and autoincrement set to true. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-284) Transformation editor should preserve any valid text formatting created by the user, especially when working with virtual procedures

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-284?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-284: ---------------------------------- Fix Version/s: 8.0 (was: 7.1) > Transformation editor should preserve any valid text formatting created by the user, especially when working with virtual procedures > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-284 > URL: https://jira.jboss.org/browse/TEIIDDES-284 > Project: Teiid Designer > Issue Type: Feature Request > Components: Diagrams > Reporter: Michael Walker > Fix For: 8.0 > > Attachments: transformationexample.JPG > > > In the transformation editor, we should preserve any valid formatting created by the user, including: > i. Whitespace > ii. Tabs > iii. Spaces > iv. Capitalization > v. Name qualification (e.g. if they don't use fully-qualified names and it's not required for validation, then preserve it) > This is especially important for virtual procedure editing, though it should extend to any transformation editing. Currently, when a user validates their virtual procedure, we wipe out all these changes, which drives them crazy. > Even worse, if the procedure doesn't validate correctly, we remove our standard tabbed/spaced formatting, and the entire procedure becomes one gigantic string without carriage returns. This is very difficult to read, especially when working with any sizable procedure, and makes the debugging process nearly impossible. See screenshot. > Most users at Genentech that develop stored procedures are literally copying and pasting the procedure code back and forth between notepad and Designer to avoid this issue. This is a severe usability defect. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-269) Import DDL

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-269?page=com.atlassian.jira.plugin... ] Barry LaFond reassigned TEIIDDES-269: ------------------------------------- Assignee: John Verhaeg > Import DDL > ---------- > > Key: TEIIDDES-269 > URL: https://jira.jboss.org/browse/TEIIDDES-269 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Marc Shirley > Assignee: John Verhaeg > Fix For: 7.1 > > > Just need to make sure we do it really well -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-469) Modify WSDL Management

by John Verhaeg (JIRA)

Modify WSDL Management ---------------------- Key: TEIIDDES-469 URL: https://jira.jboss.org/browse/TEIIDDES-469 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.3 Reporter: John Verhaeg Fix For: 7.1 Need to change web service metamodel and/or annotation handling to include generation of WSDL URL that used to be in VDB Also need to deal with generation of WSDL and WAR somewhere. -- 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

15 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-484) Error adding model to a vdb

by Steve Hawkins (JIRA)

Error adding model to a vdb --------------------------- Key: TEIIDDES-484 URL: https://jira.jboss.org/browse/TEIIDDES-484 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Reporter: Steve Hawkins Starting with a new project and an empty vdb, I created a new empty physical relational model and added it to the vdb. The resulting exception was: java.lang.RuntimeException: javax.xml.bind.MarshalException - with linked exception: [org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.] at com.metamatrix.core.modeler.CoreModelerPlugin.throwRuntimeException(CoreModelerPlugin.java:64) at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:46) at org.teiid.designer.vdb.Vdb.save(Vdb.java:365) at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor.doSave(VdbEditor.java:556) at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:151) at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:274) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2579) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:282) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:261) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:156) at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1357) at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:3328) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3341) at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:76) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) 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.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:470) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:510) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1467) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1175) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1200) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1185) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1212) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:706) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2837) at org.eclipse.swt.widgets.Button.gtk_key_press_event(Button.java:439) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1570) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4587) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4191) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:7588) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1185) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1860) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3110) 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: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:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) Caused by: javax.xml.bind.MarshalException - with linked exception: [org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.] at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:317) at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:243) at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:75) at org.teiid.designer.vdb.Vdb$2.tryToDo(Vdb.java:390) at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:37) ... 66 more Caused by: org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:410) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3165) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.addDefaultAttributes(XMLSchemaValidator.java:2859) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2041) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:685) at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(ValidatorHandlerImpl.java:549) at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527) at com.sun.xml.internal.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.java:113) at com.sun.xml.internal.bind.v2.runtime.output.ForkXmlOutput.endStartTag(ForkXmlOutput.java:91) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.endAttributes(XMLSerializer.java:294) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:686) at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54) at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157) at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:141) at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:321) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:687) at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54) at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157) at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:141) at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:321) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:581) at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:309) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:482) at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:314) ... 70 more -- 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

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-190) There is no way to hand model a XML-Relational source.

by John Doyle (JIRA)

There is no way to hand model a XML-Relational source. ------------------------------------------------------ Key: TEIIDDES-190 URL: https://jira.jboss.org/jira/browse/TEIIDDES-190 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.0.0 Reporter: John Doyle Fix For: 6.1.1 We used to ship the model extensions for XML-R modeling with the importer, and now we generate them on demand with the importer. However, if a user needs to hand model from scratch, perhaps because there is no XSD, there is no model extension to depend on. We need to provide a way to create just the extension. -- 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

15 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-456) Create ConnectionProfiles from deployed VDBs

by John Doyle (JIRA)

Create ConnectionProfiles from deployed VDBs -------------------------------------------- Key: TEIIDDES-456 URL: https://jira.jboss.org/browse/TEIIDDES-456 Project: Teiid Designer Issue Type: Sub-task Affects Versions: 7.0 Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Assume that a VDB is deployed and running in Teiid. In order to test the VDB in the DTP views a ConectionProfile must be created. This can already be done by the user manually, but in the case where a user is deploying from Designer we want the ability to create a ConnectionProfile for the user. This is an intermediate step before invoking the Database Development perspective for query testing. -- 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

15 years, 9 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2010