October 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-663) Would be cool if Dependency Diagram showed materialized view dependencies

by Ken Johnson (JIRA)

Would be cool if Dependency Diagram showed materialized view dependencies ------------------------------------------------------------------------- Key: TEIIDDES-663 URL: https://jira.jboss.org/browse/TEIIDDES-663 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 7.1 Environment: JBDS 4 Beta 1, RHEL 6 Reporter: Ken Johnson Priority: Minor When a dependency diagram is generated, it would be cool to show materialized view dependencies. Perhaps using some other representation like dashed line, grayed out, something else. This way a user can display a transformation hierarchy and at a glance tell which views have been materialized and what physical model represents the staged data. -- 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
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-660) Preview WSDL action enabled for non-web-service tables

by Barry LaFond (JIRA)

Preview WSDL action enabled for non-web-service tables ------------------------------------------------------ Key: TEIIDDES-660 URL: https://jira.jboss.org/browse/TEIIDDES-660 Project: Teiid Designer Issue Type: Bug Components: Web Services Support Affects Versions: 7.1.1 Reporter: Barry LaFond Assignee: Ted Jones Fix For: 7.1.1 Select Virtual Table in Model explorer Right-click show Modeling > XXX menu Preview WSDL shows up and it probably shouldn't Executing the action will result in Exception -- 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
3
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-256) Teiid is making column names upper case, even when specified as lower

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-256?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDDES-256. ------------------------------------- Fix Version/s: 7.1 Resolution: Done Marking as resolved as per the last comment. There may still be issues with name casing though as Teiid is case insensitive with its identifiers. > Teiid is making column names upper case, even when specified as lower > --------------------------------------------------------------------- > > Key: TEIIDDES-256 > URL: https://jira.jboss.org/browse/TEIIDDES-256 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 6.2.0 > Environment: Fedora 12, OpenJDK Server VM (build 14.0-b16, mixed mode), Teiid build 1/19/2010 > Reporter: Paul Nittel > Fix For: 7.1 > > Attachments: TextMetadataTesting.zip > > > I've got a transformation that defines two columns like this: > SELECT > c_count, COUNT(*) AS custdist > FROM > (SELECT C_CUSTKEY, COUNT(O_ORDERKEY) AS c_count FROM TPCR.CUSTOMER LEFT OUTER JOIN TPCR.ORDERS ON C_CUSTKEY = O_CUSTKEY AND O_COMMENT NOT LIKE '%special%requests%' GROUP BY C_CUSTKEY) AS c_orders > GROUP BY c_count > In the past, when queried (SELECT * FROM ...), the columns were spelled c_count and custdist. Now they're spelled C_COUNT and custdist. Do we now upcase column names that are not specified as an alias (or do we only preserve case on aliases)? > I noticed this in AdminShell, but see the Designer is also doing it, so I'm thinking it's the query engine, not the tool. (Steve H. agreed it should still be lower case when queried.) -- 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
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-328) Maximum Result Rows default is unlimited in Designer, 10, 000 in Console

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-328?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDDES-328. ------------------------------------- Resolution: Out of Date Max result rows was elevated to an engine property. > Maximum Result Rows default is unlimited in Designer, 10,000 in Console > ----------------------------------------------------------------------- > > Key: TEIIDDES-328 > URL: https://jira.jboss.org/browse/TEIIDDES-328 > Project: Teiid Designer > Issue Type: Bug > Environment: Fedora 10, build 3237 > Reporter: Paul Nittel > > I ran the TPCR test which specifies setting the Maximum result Rows property to 7,000,000. The connector binding the Designer created showed blanks for the Max. When I ran the queries, they all passed. When I deployed the VDB to the Console, Maximum Result Rows was the old default of 10,000. > They should be the same, IMHO. Or, I'd make the Designer default 10,000 and the Console's unlimited. -- 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
0
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] Resolved: (TEIIDDES-287) The modeler doesn't use the same criteria for displaying properties as the console

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-287?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDDES-287. ------------------------------------- Resolution: Out of Date The console no longer exists. > The modeler doesn't use the same criteria for displaying properties as the console > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-287 > URL: https://jira.jboss.org/browse/TEIIDDES-287 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Minor > > The console uses the 'Hidden' property to hide/show additional properties. Whereas the modeler shows an 'Expert' toggle. It would be good if they had consistent properties displays. -- 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
0
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-655) Closing Project with VDB Editor open results in SWT exceptions

by Barry LaFond (JIRA)

Closing Project with VDB Editor open results in SWT exceptions -------------------------------------------------------------- Key: TEIIDDES-655 URL: https://jira.jboss.org/browse/TEIIDDES-655 Project: Teiid Designer Issue Type: Bug Components: Editors, VDB & Execution Affects Versions: 7.1.1 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.1.1 With open project and VDB Editor open perform "Close Project" action Get SWT exceptions coming from a VDB property change listener.... at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1444) at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor.vdbNotification(VdbEditor.java:974) at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$27$1.run(VdbEditor.java:920) Turns out the VdbEntry() constructor's resource change listener is firing a change event for the deleted models. Need to add a check using "ResourceChangeUtilities.isProjectClosing(event)" and NOT fire events which would cause this vdb viewer refresh. -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-653) Renaming a folder in Model Project in Model Explorer results in ClassCastException

by Barry LaFond (JIRA)

Renaming a folder in Model Project in Model Explorer results in ClassCastException ---------------------------------------------------------------------------------- Key: TEIIDDES-653 URL: https://jira.jboss.org/browse/TEIIDDES-653 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.1.1 Attachments: rename-folder-log.txt Create Folder in Model Project Select and "Refactor > Rename" the folder Should get attached ClassCastException on finish. -- 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
3
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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2010