April 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-175) Define a contract beween Teiid and Designer that enables Designer to use different versions of Teiid.

by John Doyle (JIRA)

Define a contract beween Teiid and Designer that enables Designer to use different versions of Teiid. ----------------------------------------------------------------------------------------------------- Key: TEIIDDES-175 URL: https://jira.jboss.org/jira/browse/TEIIDDES-175 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Reporter: John Doyle Teiid Designer should be able to execute models/VDBs with different versions of Teiid. In order to accomplish this in a user friendly manner, a contract should be agreed upon between Teiid and Designer. Designer could invoke Teiid via this contract and the user would be able to easily repoint Designer to different versions of Teiid in order to test models/VDBs across different versions. -- 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
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-173) In-line rename not enabled for newly created Web Service Operation

by Barry LaFond (JIRA)

In-line rename not enabled for newly created Web Service Operation ------------------------------------------------------------------ Key: TEIIDDES-173 URL: https://jira.jboss.org/jira/browse/TEIIDDES-173 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Priority: Minor Fix For: Future 1) Open Web Service Model in Model Editor 2) Select Web Service Interface in Model explorer 3) Right-click select New > Child > Operation 4) New Operation shows up in Explorer, but auto-rename is not enabled. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-113) Ability to create partial copy of a model with new model wizard

by Barry LaFond (JIRA)

Ability to create partial copy of a model with new model wizard --------------------------------------------------------------- Key: TEIIDDES-113 URL: https://jira.jboss.org/jira/browse/TEIIDDES-113 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.0 Reporter: Barry LaFond Need to be able to create a new model from existing model (copy) and weed-out unwanted model children. Designer 5.5.3 version contained this feature, but after further review, the design was incomplete and has resulted in multiple bugs. So, plan is to remove this feature for the 6.0.0 release and then re-design & implement 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
4
0 / 0

[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, 10 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, 10 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, 10 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2010