January 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1221) Create an Advisor View that can monitor state for a given context and use-case

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1221: -------------------------------------- Summary: Create an Advisor View that can monitor state for a given context and use-case Key: TEIIDDES-1221 URL: https://issues.jboss.org/browse/TEIIDDES-1221 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Reporter: Barry LaFond Priority: Critical Attachments: project-advisor-example.png To aid in helping users go E2E for various use cases an "Advisor" view, similar to the old MM Dimension VDB-Centric product would be useful. Could be project-centric, or VDB-centric but would have to clarify the target use-cases. Attaching a screen-cap sample for single-project-centric Advisor which includes: - Status icon for each item/step. Tooltip includes summary of the OK, Warning or Error message - Quick-help icon for each item with action tooltip and selection pop-up menu of available/applicable actions - Bottom section containing applicable Cheat Sheet links -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
5
0 / 0

[JBoss JIRA] (TEIIDDES-1223) Create SQL String Template framework and dialog for use in new view construction and SQL editing

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1223: -------------------------------------- Summary: Create SQL String Template framework and dialog for use in new view construction and SQL editing Key: TEIIDDES-1223 URL: https://issues.jboss.org/browse/TEIIDDES-1223 Project: Teiid Designer Issue Type: Sub-task Components: Transformations Affects Versions: 7.6 Reporter: Barry LaFond Could be beneficial to expose a standard library of SQL templates that Designer knows about and uses in our import and object creation wizards. EXAMPLES include forms based on : SELECT * FROM XXXX SELECT a,b,c FROM t1, t2 WHERE t1.a = t2.b ======= Generated XML File Importer SQL ========== SELECT A.x AS x, A.y AS y FROM (EXEC MP.getTextFiles('myfile.xml')) AS f, XMLTABLE('/topelement/secondelement' PASSING XMLPARSE(DOCUMENT f.file) COLUMNS x string PATH '/x', y string PATH '/elem_a/elem_b') AS A ======================== -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
8
0 / 0

[JBoss JIRA] (TEIIDDES-1194) Provide query plan for the preview queries

by Ramesh Reddy (Created) (JIRA)

Provide query plan for the preview queries ------------------------------------------ Key: TEIIDDES-1194 URL: https://issues.jboss.org/browse/TEIIDDES-1194 Project: Teiid Designer Issue Type: Feature Request Components: Data Preview Affects Versions: 7.6 Reporter: Ramesh Reddy Currently there no way to see the query plan for the queries executed using preview feature. This request has come up couple times from users as it is most important to see the query plan while developing the transformation and see where the significant bottlenecks are. Currently the only way one can see query plan in designer is to deploy the VDB and issue the query using the DTP and then view the query plan. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-942) Need better indication of Error in Query Plan retrieval

by Mark Drilling (JIRA)

Need better indication of Error in Query Plan retrieval ------------------------------------------------------- Key: TEIIDDES-942 URL: https://issues.jboss.org/browse/TEIIDDES-942 Project: Teiid Designer Issue Type: Enhancement Components: Datatools Integration Affects Versions: 7.1.1 Reporter: Mark Drilling Priority: Minor It should be obvious to the user on the "Execution Plan" tab if a query error prevents retrieval of the Query Plan. - Executed a user query. The Execution Plan just showed the original SQL and nothing else... - Further examination of the server log showed plan debug output, but there was a source error on execution - I switched over to the "Message Log" tab in designer to find the message "An exception occurred fetching the Query Plan" Request that the Execution Plan tab show a problem message, instead of just showing the original SQL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-987) Add ability to edit/generate Create Virtual Procedure statements for RestEasy XML, File Translator and Web Service Translator procedures

by Barry LaFond (JIRA)

Add ability to edit/generate Create Virtual Procedure statements for RestEasy XML, File Translator and Web Service Translator procedures ---------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-987 URL: https://issues.jboss.org/browse/TEIIDDES-987 Project: Teiid Designer Issue Type: Enhancement Components: Editors, Transformations Affects Versions: 7.4 Reporter: Barry LaFond Fix For: 7.5 Designer includes "Generate xxxx procedures" options in the New Model Wizard. Also have a RestEasy use-case that requires getXXXX virtual procedures that contain SQL like: CREATE VIRTUAL PROCEDURE BEGIN SELECT XMLELEMENT(NAME parts, XMLAGG(XMLELEMENT(NAME part, XMLFOREST(VirtualParts_Supplier.PARTS.PART_ID, VirtualParts_Supplier.PARTS.PART_NAME, VirtualParts_Supplier.PARTS.PART_COLOR, VirtualParts_Supplier.PARTS.PART_WEIGHT)))) AS result FROM VirtualParts_Supplier.PARTS WHERE VirtualParts_Supplier.getParts.partId_in = VirtualParts_Supplier.PARTS.PART_ID; END Would be nice to have a framework where "wizards" can be accessed to create/edit the content of this SQL if the basic structure is a Set Query (SELECT * FROM XXX)for these specific use-cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
9
0 / 0

[JBoss JIRA] (TEIIDDES-1199) New Teiid Instance: Admin test doesn't indicate it's admin (and more)

by Paul Nittel (Created) (JIRA)

New Teiid Instance: Admin test doesn't indicate it's admin (and more) --------------------------------------------------------------------- Key: TEIIDDES-1199 URL: https://issues.jboss.org/browse/TEIIDDES-1199 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.6 Reporter: Paul Nittel Priority: Minor MINOR ISSUE: When creating a Teiid server instance, clicking the Test button tests both the admin and user (JDBC) connections. Each test results in a dialog popping up. The user connection test clearly indicates it's for the user (JDBC) connection. The test of the admin connection never mentions the word "admin". MAKING THINGS BETTER: Is it possible to have both tests reported in a single dialog? It would be far clearer to the user and less annoying since the user is not likely to expect the second dialog to appear. THE BUG: If the admin connection test fails (bad username, for example), the JDBC connection test is also shown as failing, even when its connection information is correct -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1043) Test Connection on LDAP Connection Profile Wizard page does not enable

by Barry LaFond (JIRA)

Test Connection on LDAP Connection Profile Wizard page does not enable ---------------------------------------------------------------------- Key: TEIIDDES-1043 URL: https://issues.jboss.org/browse/TEIIDDES-1043 Project: Teiid Designer Issue Type: Bug Components: Datatools Integration Affects Versions: 7.4, 7.5, 7.4.2 Reporter: Barry LaFond Fix For: 7.6 Filling in required info in new LDAP connection profile does not enable the "Test Connection" button. Looks like a "setPingButtonEnabled(true);" call needs to be made at the end of the LdapProfileDetailsWizardPage.validate() method, but adding the code ends up throwing an NPE when pressed. So, it looks like there is no IConnectionFactoryProvider/IConnectionFactory contributed for the LDAP connection to use to "ping" the DB. This would have to be completed in order for the Test Connection button to not throw an NPE -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
6
0 / 0

[JBoss JIRA] (TEIIDDES-1228) Create Preview Data Dialog

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1228: -------------------------------------- Summary: Create Preview Data Dialog Key: TEIIDDES-1228 URL: https://issues.jboss.org/browse/TEIIDDES-1228 Project: Teiid Designer Issue Type: Feature Request Components: Data Preview Affects Versions: 7.7 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.7 Working with Advisor-type view and Action Library View, it seems we need a dialog to handle allowing Preview Data action to be executed WITHOUT pre-selecting a table or procedure. So create a dialog that queries the user to select a table or wizard from the workspace first, then executes the Preview Data action. Probably should include - check for "Server Exists" (i.e. if so, then "ping()" to verify preview could run. - Allow selection of only previewable objects (Tables and procedures) - validate each selection. If "ERROR" then don't allow "OK" or maybe change the "OK" to "Execute"?? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
3
0 / 0

[JBoss JIRA] (TEIIDDES-1225) 'Add MED to Registry' action allows attempt to add an invalid MED to the registry

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1225: --------------------------------------- Summary: 'Add MED to Registry' action allows attempt to add an invalid MED to the registry Key: TEIIDDES-1225 URL: https://issues.jboss.org/browse/TEIIDDES-1225 Project: Teiid Designer Issue Type: Bug Components: Extension Framework Affects Versions: 7.7 Reporter: Mark Drilling The 'Add MED to Registry' action looks at the mxd problem markers before doing the add operation. However, if the workspace has not been built the file may not have a problem marker. This results in attempt to add an invalid MED to the registry. We should not allow the process to get that far - ensure the build is complete or check for errors in a different manner. Example usage is in ModelExtensionDefinitionEditor.createActions, which uses RegistryDeploymentValidator.checkProblemMarkers to do this check currently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] (TEIIDDES-1226) Removal of SF builtIn MED from SFModel results in empty model file

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1226: --------------------------------------- Summary: Removal of SF builtIn MED from SFModel results in empty model file Key: TEIIDDES-1226 URL: https://issues.jboss.org/browse/TEIIDDES-1226 Project: Teiid Designer Issue Type: Bug Components: Extension Framework Affects Versions: 7.7 Reporter: Mark Drilling Fix For: 7.7 Encountered a problem removing the SF MED from an imported SF Model. On Finish from the ManageMEDs wizard, got NPE (attached) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2012