August 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-585) Remove XML Service metamodel as it is no longer used.

by Ken Johnson (JIRA)

Remove XML Service metamodel as it is no longer used. ----------------------------------------------------- Key: TEIIDDES-585 URL: https://jira.jboss.org/browse/TEIIDDES-585 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Environment: JBTools Aug 26, 2010. Eclipse 3.6, RHEL 6 Beta Reporter: Ken Johnson The XML Service metamodel is no longer used for sourcing XML data. It should be removed from Designer. -- 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

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-191) XSD as Relational importer has problems with child elements with many parents

by Greg Haber (JIRA)

XSD as Relational importer has problems with child elements with many parents ----------------------------------------------------------------------------- Key: TEIIDDES-191 URL: https://jira.jboss.org/jira/browse/TEIIDDES-191 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: Teiid Designer 6.0.0 official (14 May 2009) release Reporter: Greg Haber Attachments: address.xsd, person.xsd, person2.xml, person2.xsd I've encountered a lot of problems with the Teiid Designer XML as Relational Importer (and with its legacy ancestor) dealing with importing XSDs where a child element has multiple parents. The importer currently treats all elements throughout the XSD that have the same name and type as the same, and so models that element(s) as a single table with multiple parents, if the number of parents is above a configurable number (currently defaults to 3). Which is all well and good in theory, but in practice it seems to hit a number of problems 1) During the import process, if the selection of document root elements is left at the default, not all needed tables are generated. See person.xsd example attached. 2) If all possible root elements are selected, it looks mostly right, but there are often extra elements in the child tables (again try with person.xsd). Plus, the tables don't actually work at runtime correctly (try using attached person2.xml as the data source - notice that you can only get to the spouse's father from Person, not to their own father). I've also attached some other example problem XSDs - person2.xsd, and address.xsd Now, in some cases a reasonable workaround is to up the number of allowed parents parameter, so that everything gets folded into a single table. But that isn't a general solution, as it doesn't work with things like person2.xsd. -- 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

12 years, 3 months

2
4
0 / 0

[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

12 years, 8 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

12 years, 8 months

3
6
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

12 years, 9 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

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-165) Transformations Dependent On UDF Model Are Not Validated When UDF Model Changes And Build Is Run

by Dan Florian (JIRA)

Transformations Dependent On UDF Model Are Not Validated When UDF Model Changes And Build Is Run ------------------------------------------------------------------------------------------------ Key: TEIIDDES-165 URL: https://jira.jboss.org/jira/browse/TEIIDDES-165 Project: Teiid Designer Issue Type: Bug Components: Modeling, Transformations, Validation Affects Versions: 6.0.0 Reporter: Dan Florian When you delete a function from the UDF model that is being used by a transformation, there is no warning dialog saying that another model is dependent on that function. When you then save the UDF model and a run a build, no validation errors occur indicating a transformation is using an invalid function. You have to clean the workspace or edit the model containing the transformation in order to finally get a validation error. -- 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

12 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-181) Missing Java SQL Types In RelationalTypeMapping Interface And Implementation Class

by Dan Florian (JIRA)

Missing Java SQL Types In RelationalTypeMapping Interface And Implementation Class ---------------------------------------------------------------------------------- Key: TEIIDDES-181 URL: https://jira.jboss.org/jira/browse/TEIIDDES-181 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Reporter: Dan Florian The following java.sql.Types constants do not have constants in RelationalTypeMapping or mappings in RelationalTypeMappingImpl: DATALINK, BOOLEAN, ROWID, LONGNVARCHAR, NCLOB, and SQLXML. All but the first 2 were added in JDK 1.6. Need to provide the mapping to the metamatrix datatypes for each or determine a mapping is not needed. Also may want to look at using or referencing com.metamatrix.common.types.MMJDBCSQLTypeInfo instead of maintaining the mapping in two differenct classes. See TEIIDDES-179 where NVARCHAR was added to fix this defect. -- 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

12 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-229) Textual Metadata Importer fails to create simple virtual table transformations

by Paul Nittel (JIRA)

Textual Metadata Importer fails to create simple virtual table transformations ------------------------------------------------------------------------------ Key: TEIIDDES-229 URL: https://jira.jboss.org/jira/browse/TEIIDDES-229 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.2.0 Environment: Fedora 10, Designer build 20090922 Reporter: Paul Nittel Importing the attached file into the VQT model of the attached model project set concludes wit mixed results. Some of the transformations are success while others fail. Even the simplest fail. The results appear to be very consistent as I've tried this a few time with the same outcome. 1 - Start Designer 2 - Import model project set 3 - Select VQT model 4 - Right-click VQT > Import > Metadata from Text 5 - Follow the Wizard 6 - Navigate to, and choose, the VqtTransformationSqlForTextImport.txt file 7 - Select the VQT model 8 - Finish In my case, the MAPPING tables (1 - 4) each have null transformations. Copying and pasting in the transformations specified in the file all work. -- 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

12 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-260) Problems in New Model Wizard after backing up to Select different Metamodel type

by Barry LaFond (JIRA)

Problems in New Model Wizard after backing up to Select different Metamodel type -------------------------------------------------------------------------------- Key: TEIIDDES-260 URL: https://jira.jboss.org/jira/browse/TEIIDDES-260 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Open Designer and make sure you have a Relational and Web service model in workspace (i.e. import relational and create WS via "Modeling >> Create Web Service" action. 1) Select "New Metadata Model" 2) Select "Relational" metamodel and "Source" model type (click NEXT) 3) Select Relational model in workspace (via "..." browse button) (notice selecting non-relational models results in error message in model selection dialog) (click OK) 4) Select "Back" button to return to selecting model types 5) Select "Web Service" metamodel (click NEXT) 6) Select Web Service model in workspace (via "..." browse button). 7) Note that error message says that user must select a "Relational" model. This is wrong and basically the MetaModelDescriptor isn't getting updated on the StructuralCopyWizard & TreeViewerWizardPanel. -- 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

12 years, 10 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2010