June 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-199) Add versioning info to the generated modelextensions.

by John Doyle (JIRA)

Add versioning info to the generated modelextensions. ----------------------------------------------------- Key: TEIIDDES-199 URL: https://jira.jboss.org/jira/browse/TEIIDDES-199 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.0.0 Reporter: John Doyle Assignee: John Doyle Fix For: 6.1.0 The model extension should have a version number so that change can be accounted for in later 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

15 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-464) Teiid 7.0 XML integration issues

by Steve Hawkins (JIRA)

Teiid 7.0 XML integration issues -------------------------------- Key: TEIIDDES-464 URL: https://jira.jboss.org/browse/TEIIDDES-464 Project: Teiid Designer Issue Type: Quality Risk Components: Import/Export, Modeling, Teiid Integration Affects Versions: 7.0 Reporter: Steve Hawkins Priority: Critical With Teiid 7.0 there are several changes that affect functionality provided in the designer: 1. The xml imports (relational or source) are now invalid. There is now engine functionality to handle row extraction. If possible these importers should be retargeted. 2. The xquery web services model is now invalid. XQuery is now executed through the XMLQUERY expression, so the command type is just regular SQL - not XQuery. -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-471) Turn on Nightly Tests

by John Verhaeg (JIRA)

Turn on Nightly Tests --------------------- Key: TEIIDDES-471 URL: https://jira.jboss.org/browse/TEIIDDES-471 Project: Teiid Designer Issue Type: Task Components: Housekeeping Affects Versions: 6.3 Reporter: John Verhaeg Fix For: 7.0 We have enough new tests now that we can depend on going forward, so at least some test projects need to be built and run each night. -- 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, 6 months

5
12
0 / 0

[JBoss JIRA] Created: (TEIIDDES-214) Validate that the jdbc4olap driver works as expected in Designer and Teiid.

by John Doyle (JIRA)

Validate that the jdbc4olap driver works as expected in Designer and Teiid. --------------------------------------------------------------------------- Key: TEIIDDES-214 URL: https://jira.jboss.org/jira/browse/TEIIDDES-214 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: John Doyle Assignee: John Doyle http://www.jdbc4olap.org/ provides a type 4 JDBC driver for OLAP sources that support XMLA. Supporting this driver will provide access to many OLAP sources (SAP, Microsoft, Mondrian) Currently the only OLAP source that we have tested with is SAP BW via the OLAP BAPI interface. Those BAPIs are procedural and require the model designer to create extensive procedural logic in their models. jdbc4olap should enable a user to access OLAP data via standard JDBC semantics. -- 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, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-403) Eliminate use of restricted Eclipse classes

by Barry LaFond (JIRA)

Eliminate use of restricted Eclipse classes ------------------------------------------- Key: TEIIDDES-403 URL: https://jira.jboss.org/jira/browse/TEIIDDES-403 Project: Teiid Designer Issue Type: Sub-task Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Designer still uses some restricted Eclipse classes. Goal is to become compliant with the restrictions. -- 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, 8 months

2
8
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-481) Checkboxes in VDB editor for Synch and visibility are "unusual" and never checked

by Paul Nittel (JIRA)

Checkboxes in VDB editor for Synch and visibility are "unusual" and never checked --------------------------------------------------------------------------------- Key: TEIIDDES-481 URL: https://jira.jboss.org/browse/TEIIDDES-481 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.0 Environment: Fedora 12, OpenJDK, Milestone build from 6/28 Reporter: Paul Nittel 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. See attached screenshot.) 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. 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-476) JDBC Importer no longer provides ability to edit connection information

by John Verhaeg (JIRA)

JDBC Importer no longer provides ability to edit connection information ----------------------------------------------------------------------- Key: TEIIDDES-476 URL: https://jira.jboss.org/browse/TEIIDDES-476 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.0 Reporter: John Verhaeg Fix For: 7.0 After creating a connection profile via the JDBC importer dialog, I could no longer go back and edit its values (such as password). -- 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, 11 months

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2010