January 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-116) Add ability to perform partial copy model operations in new model wizard

by Barry LaFond (JIRA)

Add ability to perform partial copy model operations in new model wizard ------------------------------------------------------------------------ Key: TEIIDDES-116 URL: https://jira.jboss.org/jira/browse/TEIIDDES-116 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: 6.1.0 -- 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

1
2
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-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, 9 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, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-189) Plugin details shows version, but not build number

by Paul Nittel (JIRA)

Plugin details shows version, but not build number -------------------------------------------------- Key: TEIIDDES-189 URL: https://jira.jboss.org/jira/browse/TEIIDDES-189 Project: Teiid Designer Issue Type: Bug Components: Build Affects Versions: 6.0.0 Environment: Fedora 10 Reporter: Paul Nittel Since the plugin details shows only the version (6.0.0), there is no way to determine from which build this came. We really need this ability back. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-171) VDB Editor allows adding multiple Salesforce generated relational models.

by Barry LaFond (JIRA)

VDB Editor allows adding multiple Salesforce generated relational models. ------------------------------------------------------------------------- Key: TEIIDDES-171 URL: https://jira.jboss.org/jira/browse/TEIIDDES-171 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: 6.1.0 While investigating TEIIDDES-168, I tried to add a second Salesforce model to a VDB. I had already added "sf.xmi" which auto-added the XMLSOAPConnectorExtensions.xmi model. But adding "stock.xmi", which depends on a DIFFERENT XMLSOAPConnectorExtensions.xmi file, it added "stock.xmi" thinking it already had the right XMLSOAPConnectorExtensions.xmi file. So, there is a bug here where VDB Editor should have detected the actual dependent XMLSOAPConnectorExtensions.xmi file and NOT allowed adding stock.xmi -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-126) Add a warning for the use of a model supports property

by Steven Hawkins (JIRA)

Add a warning for the use of a model supports property ------------------------------------------------------ Key: TEIIDDES-126 URL: https://jira.jboss.org/jira/browse/TEIIDDES-126 Project: Teiid Designer Issue Type: Quality Risk Components: Modeling Affects Versions: 6.0.0 Reporter: Steven Hawkins See TEIID-131. Model support properties that are simply overrides for connector binding properties are no longer checked by the Teiid runtime, rather TEIID-205 is used to control specific capabilities through the connector binding without requiring the creation of a custom capabilities class. Usage of 'Set Criteria Max Size', Supports "Distinct', Supports "Join", Supports "Order By", Supports "Outer Join", and Supports "Where all" should generate a warning stating that the connector binding should be used instead. -- 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
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2010