March 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-530) The LDAP documentation in MMx that relates to designer activity, needs to be included in the designer documentation

by Van Halbert (JIRA)

The LDAP documentation in MMx that relates to designer activity, needs to be included in the designer documentation ------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-530 URL: https://jira.jboss.org/browse/TEIIDDES-530 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.0 Reporter: Van Halbert There is MMx LDAP documentation that relates to what has to be done in the designer in order to model a LDAP data source. This documentation needs to be brought over into designer documentation. -- 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-579) SQL Scrapbook created from Teiid connection is created with Ingress_2006 as the Connection Profile type.

by John Doyle (JIRA)

SQL Scrapbook created from Teiid connection is created with Ingress_2006 as the Connection Profile type. -------------------------------------------------------------------------------------------------------- Key: TEIIDDES-579 URL: https://jira.jboss.org/browse/TEIIDDES-579 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1 If you right click on a Teiid connection in the Data Source Explorer and open a SQL Scrapbook, the scrapbook page is not created with a Teiid Connection Profile Type, it is created with an Ingress_2006 type. -- 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

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-597) Insert Rows in relational column table editor creates columns in reverse order

by Paul Nittel (JIRA)

Insert Rows in relational column table editor creates columns in reverse order ------------------------------------------------------------------------------ Key: TEIIDDES-597 URL: https://jira.jboss.org/browse/TEIIDDES-597 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Fix For: 7.1.1 Attachments: OutOfOrder.png (This has been an issue for a long time, but I don't see a current bug, so here's a new one!) If a user chooses to edit relational columnar metadata in teh table editor and Inserts Rows, they are inserted in reverse order. (See the attached screenshot.) In this case I inserted 8 rows. They're shown int eh tree in the correct order but arte inverted in the table editor. It's just wrong. -- 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

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-908) Replace Salesforce Extension Model created during import

by Barry LaFond (JIRA)

Replace Salesforce Extension Model created during import --------------------------------------------------------- Key: TEIIDDES-908 URL: https://issues.jboss.org/browse/TEIIDDES-908 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.4 In order to simplify JDBC import processing by replacing Designer's RelationalModelProcessor with Teiid's processor, the Salesforce Import use-case needs to be simplified by removing the need to have a separate Extension model. TEIIDDES-905 is providing a new extension model framework that eliminates the need for a separate model. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
14
0 / 0

[JBoss JIRA] Created: (TEIIDDES-714) Designer should clean up preview vdbs every time Teiid Server connection is made.

by Ramesh Reddy (JIRA)

Designer should clean up preview vdbs every time Teiid Server connection is made. --------------------------------------------------------------------------------- Key: TEIIDDES-714 URL: https://jira.jboss.org/browse/TEIIDDES-714 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.1 Reporter: Ramesh Reddy It is quite possible that that the preview vdbs deployed into a Teiid Server get out of sync with the Designer when the Server is restarted independent of the Designer. Since Designer keeps track of its preview vdbs based on workspace uuid, it is better that it cleans up its preview vdbs and data sources when the connection is made and connection is cleaned up. These actions may happen at both startup and shutdown of the Designer and also at the creation and discard of the Server settings once the Designer started. Otherwise there may be orphan VDBs left over in the Server. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-704) NPE while constructing XML Documents from old/custom Parts XML Schema

by Barry LaFond (JIRA)

NPE while constructing XML Documents from old/custom Parts XML Schema --------------------------------------------------------------------- Key: TEIIDDES-704 URL: https://jira.jboss.org/browse/TEIIDDES-704 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Reporter: Barry LaFond Fix For: 7.2 TEIIDDES-664 exposed a problem with displaying a error dialog when XML Document creation fails. This was fixed. What's not fixed is the NPE that is resulting from the schema involved. See attached Schema and create an XML Document from the PartOrder root element. Exception in thread "ModelBuffer.Save" java.lang.NullPointerException at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getURIFragment(XMLHelperImpl.java:719) at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getIDREF(XMLHelperImpl.java:753) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveIDRefSingle(XMLSaveImpl.java:1972) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveIDRefSingle(MtkXmiSaveImpl.java:298) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1318) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:90) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:592) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:256) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:206) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiResourceImpl.doSave(MtkXmiResourceImpl.java:354) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:1406) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl.saveInTransaction(ModelBufferImpl.java:559) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl$1.run(ModelBufferImpl.java:488) -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-776) Data Roles: After unchecking a model, cannot check subordinate metadata, like columns

by Paul Nittel (JIRA)

Data Roles: After unchecking a model, cannot check subordinate metadata, like columns ------------------------------------------------------------------------------------- Key: TEIIDDES-776 URL: https://issues.jboss.org/browse/TEIIDDES-776 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1.1 Reporter: Paul Nittel In the case where an administrator wishes to prevent access to all columns but a relatively few, they should be able to: Uncheck the model (which causes all subordinate objects to be unchecked) Check the small number to which access is desired. What happens is once the model is unchecked, the subordinate objects cannot be checked. (Also, if all subordinate objects are manually unchecked, the model has a grayed-out check as if there is a checked subordinate object. If all objects under a model are unchecked, the model itself should also be unchecked.) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-812) DDL Export XSLT files need to be upgraded/improved

by Barry LaFond (JIRA)

DDL Export XSLT files need to be upgraded/improved -------------------------------------------------- Key: TEIIDDES-812 URL: https://issues.jboss.org/browse/TEIIDDES-812 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.2, 7.1.1, 7.3 Reporter: Barry LaFond Priority: Critical Fix For: 7.4 After working import issue TEIIDDES-215, it's become apparent that our XSLT's for various DB's need to be revisited. For instance, there is no logic in PostgreSQL version to check for integer types that have AUTOINCREMENT == TRUE. These should be exported as SERIAL datatypes. Same for BIGSERIAL. There is other missing logic. We need to: 1) Create a doc or series of docs describing what datatype conversions should be done on IMPORT JDBC and EXPORT DDL 2) Create sub-tasks for implementing these docs for all DB's 3) Possibly create extension point(s) to handle "new" DB types more effeciently -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-228) Import transformation SQL fails to do anything

by Paul Nittel (JIRA)

Import transformation SQL fails to do anything ---------------------------------------------- Key: TEIIDDES-228 URL: https://jira.jboss.org/jira/browse/TEIIDDES-228 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.2.0 Environment: Fedora 10, Designer 20090922 build (same thing with RC1) Reporter: Paul Nittel I exported the transformation SQL from the VQT model. When I tried to import the SQL into a new VQT model, it gave the appearance it completed successfully, but none of the tables were defined. There were no errors or exceptions found in the log. The format of the exported file is not the same as that of the Metadata Text Importer, so to use that route the file must be edited. (The export version takes into account the SELECT, INSERT, UPDATE, DELETE possibilities.) BTW, this had issues as well, but that's another JIRA. -- 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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-166) Exceptions Displaying Just Deleted Function In Expression Builder

by Dan Florian (JIRA)

Exceptions Displaying Just Deleted Function In Expression Builder ----------------------------------------------------------------- Key: TEIIDDES-166 URL: https://jira.jboss.org/jira/browse/TEIIDDES-166 Project: Teiid Designer Issue Type: Bug Components: Modeling, Transformations Affects Versions: 6.0.0 Reporter: Dan Florian 1. In a transformation editor use a function from the UDF model. 2. Delete that same function from the UDF. 3. Save UDF model. This should do a automatic build. 4. Go back to transformation editor and put cursor in the reference to the deleted function. 5. Start the Expression Builder. 6. Get exceptions. -- 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, 8 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 March 2011