September 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-550) Import DDL to Relational Table misses columns for primary, foreign keys

by Paul Nittel (JIRA)

Import DDL to Relational Table misses columns for primary, foreign keys ----------------------------------------------------------------------- Key: TEIIDDES-550 URL: https://jira.jboss.org/browse/TEIIDDES-550 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, TeiidDesigner 7.1 M1 Reporter: Paul Nittel Attachments: motels.ddl I imported the motels.ddl example file to populate the foo model. When finished importing, I had a number of errors where the importer had created primary and foreign keys without specifying columns for those keys. In one case, here's the DDL: CREATE TABLE CustomerFamilyHistory ( customerfamilyhistoryid number(10) CONSTRAINT customerfamilyhistoryid_pk PRIMARY KEY, firstname varchar2(50) NOT NULL, lastname varchar2(50) NOT NULL, age number(3), sibling varchar2(20), customerid number(7) NOT NULL ); The primary key, customerfamilyhistoryid_pk, is created, but no reference to customerfamilyhistoryid is provided. -- 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

4
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-541) Table data preview requires all models in project to be without validation errors - should pertain only to models required for preview

by Paul Nittel (JIRA)

Table data preview requires all models in project to be without validation errors - should pertain only to models required for preview -------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-541 URL: https://jira.jboss.org/browse/TEIIDDES-541 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, Teiid 7.1M1 Reporter: Paul Nittel Attachments: LogWithPreviewErrors.log While in the middle of creating a virtual model, I attempted to preview data from an imported source model. Because the virtual model was incomplete, and thus failed validation, the preview was not possible. This is a valid use case. Preview of a model's tables should always work assuming invalid models are not required for the preview itself. Attaching the Designer's log file. -- 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

4
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-629) When creating a UDF, the Invocation class and method should be optional

by Van Halbert (JIRA)

When creating a UDF, the Invocation class and method should be optional ----------------------------------------------------------------------- Key: TEIIDDES-629 URL: https://jira.jboss.org/browse/TEIIDDES-629 Project: Teiid Designer Issue Type: Bug Components: Editors Reporter: Van Halbert According to Teiid Developer Guide, the Invocation Class and Method are optional properties, because in the cases where the function is REQUIRED to be a push down, it will never be called by the engine. Also, it would be nice for the Category, to present the list of current categories that have been defined just so you can select an already defined one (this just keeps user typing errors to minimal) or let the user override and add a new one if one if needed. -- 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-638) Rose importer unable to instantiate class "com.metamatrix.rose.internal.ui.wizard.RoseImportWizard"

by Paul Nittel (JIRA)

Rose importer unable to instantiate class "com.metamatrix.rose.internal.ui.wizard.RoseImportWizard" --------------------------------------------------------------------------------------------------- Key: TEIIDDES-638 URL: https://jira.jboss.org/browse/TEIIDDES-638 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1 Reporter: Paul Nittel Fix For: 7.1.1 I tried to import from Rose, but when I started the importer I received this exception: The selected wizard could not be started. Plug-in "org.teiid.designer.rose.ui" was unable to instantiate class "com.metamatrix.rose.internal.ui.wizard.RoseImportWizard". java.net.MalformedURLException: unknown protocol: pathmap -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-198) Error in TestServerRuntimeMetadata unit test

by Barry LaFond (JIRA)

Error in TestServerRuntimeMetadata unit test -------------------------------------------- Key: TEIIDDES-198 URL: https://jira.jboss.org/jira/browse/TEIIDDES-198 Project: Teiid Designer Issue Type: Bug Reporter: Barry LaFond Fix For: 6.1.1 Error in TestServerRuntimeMetadata.testGetXmlSchemas() method. Appears that the TreeMappingRootSqlAspect.getTransformationInfo() method is calling toUpperCase() on the Import locations. This results in an XSD file potentially having Case Sensitivity problems on LINUX, in this case. Need to investigate removing this toUpperCase() call. This has not manifested itself because it's a runtime/server thing and only happens if the XML validation is turned on which is basically not done. Our unit test happens to test ALL the basic methods and we haven't run unit tests consistently on LINUX until recently with Teiid Designer. -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-491) Procedures with ERROR 'error message text' are interpreted as assignments and then fail as Element ""ERROR"" is not defined by any relevant group

by Paul Nittel (JIRA)

Procedures with ERROR 'error message text' are interpreted as assignments and then fail as Element ""ERROR"" is not defined by any relevant group ------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-491 URL: https://jira.jboss.org/browse/TEIIDDES-491 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.0 Environment: Fedora 12, OpenJDK, Designer 6/28 Reporter: Paul Nittel I found this while testing Dynamic SQL where ERROR 'some message' is morphed into "ERROR" = 'some message' when the transformation SQL is validated. No way around it. Steve H. wonders if it's due to ERROR being inherited from assignment (or some such ;-). -- 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, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-482) Synchronizing models in a VDB does not work quite as expected

by Paul Nittel (JIRA)

Synchronizing models in a VDB does not work quite as expected ------------------------------------------------------------- Key: TEIIDDES-482 URL: https://jira.jboss.org/browse/TEIIDDES-482 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.0 Environment: Fedora 12, OpenJDK, Designer from 6/28 Reporter: Paul Nittel Attachments: SynchronizeThis.zip Assuming I have a VDB which contains models, 1 - Modify one of the models 2 - Save the model 3 - The VDB editor shows the large "Synchronize All" button is enabled and the synch checkbox associated with the changed model is an empty checkbox. (The other checkboxes are large gray squares.) 4 - Click the checkbox (it now turns into the gray square - the large "All" button remains enabled) 5 - Save the VDB Now the large "Synchronize All" button is disabled If I click the "Synchronize All" button first, the checkbox is affected and the large button remains enabled until the VDB is saved. (If I click it again, it still goes through the synch process.) I would expect the button and checkbox(es) to work together and that once all models are synched, the large button would be disabled even without the VDB being saved. (Oddly, once I save a model in the VDB, the VDB becomes dirty. Maybe this is intentional, but now I don't have the option to deploy that VDB until I synch it.) -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-511) Designer "Help About" lists Teiid's provider as "Red Hat, Inc." - Should be "JBoss by Red Hat" like the others

by Paul Nittel (JIRA)

Designer "Help About" lists Teiid's provider as "Red Hat, Inc." - Should be "JBoss by Red Hat" like the others -------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-511 URL: https://jira.jboss.org/browse/TEIIDDES-511 Project: Teiid Designer Issue Type: Task Affects Versions: 7.0 Environment: All Reporter: Paul Nittel Selecting the Teiid icon at the bottom of Help About JBoss Developer Studio brings up the Teiid features. "Red Hat, Inc." is listed as provider. For all other JBoss features, the provider is "JBoss by Red Hat". Please change so Teiid matches its sibling features. (Check the copyright information, too, please.) -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-609) Teiid QueryValidatorException opening VDB schema in Data Source Explorer for model with "hidden" table.

by Barry LaFond (JIRA)

Teiid QueryValidatorException opening VDB schema in Data Source Explorer for model with "hidden" table. ------------------------------------------------------------------------------------------------------- Key: TEIIDDES-609 URL: https://jira.jboss.org/browse/TEIIDDES-609 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Reporter: Barry LaFond Assignee: John Doyle Priority: Blocker Fix For: 7.1.1 After creating a data role for PartsSupplier VDB where the CRUD for one table was turned OFF (i.e. create/read/update/delete = FALSE) and deploying to Teiid, I deployed and executed the VDB. But on trying to view the contents in DTP, an exception occured. org.teiid.jdbc.TeiidSQLException: Error trying to obtain schema metadata info on this connection: Remote org.teiid.api.exception.query.QueryValidatorException: User <Hcs7WsIzrd4G> is not entitled to action <Read> for 1 or more of the groups/elements/procedures.. at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:102) at org.teiid.jdbc.DatabaseMetaDataImpl.getSchemas(DatabaseMetaDataImpl.java:2361) at org.teiid.jdbc.DatabaseMetaDataImpl.getSchemas(DatabaseMetaDataImpl.java:1298) at org.eclipse.datatools.connectivity.sqm.loader.JDBCSchemaLoader.createResultSet(JDBCSchemaLoader.java:174) at org.eclipse.datatools.connectivity.sqm.loader.JDBCSchemaLoader.loadSchemas(JDBCSchemaLoader.java:110) at org.eclipse.datatools.connectivity.sqm.core.rte.jdbc.JDBCCatalog.loadSchemas(JDBCCatalog.java:101) at org.eclipse.datatools.connectivity.sqm.core.rte.jdbc.JDBCCatalog.getSchemas(JDBCCatalog.java:64) at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.vnode.ServerExplorerVNodeContentProviderNav.displaySchemaNodeChildren(ServerExplorerVNodeContentProviderNav.java:126) -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-644) Books example has incorrect transformation SQL in XML document model

by Paul Nittel (JIRA)

Books example has incorrect transformation SQL in XML document model -------------------------------------------------------------------- Key: TEIIDDES-644 URL: https://jira.jboss.org/browse/TEIIDDES-644 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.1.1 Environment: JBDS 4.0.0 M2, Designer bulid H280 Reporter: Paul Nittel Fix For: 7.1.1 I imported the Books Project into my workspace and found the XML document model had errors, Checking, I found the transformation SQL referenced the wrong models. For example, SELECT Books_Oracle.AUTHORS.LASTNAME AS author FROM Books_SQLServer.BOOK_AUTHORS, Books_Oracle.AUTHORS WHERE ("input".isbn = Books_SQLServer.BOOK_AUTHORS.ISBN) AND (Books_SQLServer.BOOK_AUTHORS.AUTHOR_ID = Books_Oracle.AUTHORS.AUTHOR_ID) should reference Books_SourceA and Books_SourceB rather than Books_SQLServer and Books_Oracle. -- 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, 10 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2010