December 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-882) Create new SOAP service connection profile.

by John Doyle (JIRA)

Create new SOAP service connection profile. ------------------------------------------- Key: TEIIDDES-882 URL: https://issues.jboss.org/browse/TEIIDDES-882 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.2, 7.1, 7.3 Reporter: John Doyle For the WSDL into Relational Model Importer we take advantage of the DTP provided Web Service Data Source connection profile. We really only did this because of time constraints. That profile has attributes that don't make sense for Teiid Designer and are ignored by Designer. We really need our own dedicated connection profile that provides the correct interface to the user and enables us to satisfy existing issues we cannot solve with the DTP profile. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
13
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-1182) MED Boolean Property Definitions Should Not Store Allowed Values In The MED

by Dan Florian (Created) (JIRA)

MED Boolean Property Definitions Should Not Store Allowed Values In The MED --------------------------------------------------------------------------- Key: TEIIDDES-1182 URL: https://issues.jboss.org/browse/TEIIDDES-1182 Project: Teiid Designer Issue Type: Task Components: Editors Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.7 Created a boolean property definition in a MED and noticed the allowed values of "true" and "false" got stored with the property definition. For boolean values the allowed values need not be stored in the MED. This used to not work like this. -- 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
1
0 / 0

[JBoss JIRA] (TEIIDDES-1165) MED Editor Properties page should utilize same "Model Class" and "Model Type" combo boxes as the New Metadata Model wizard.

by Barry LaFond (Created) (JIRA)

MED Editor Properties page should utilize same "Model Class" and "Model Type" combo boxes as the New Metadata Model wizard. --------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1165 URL: https://issues.jboss.org/browse/TEIIDDES-1165 Project: Teiid Designer Issue Type: Enhancement Reporter: Barry LaFond Assignee: Dan Florian The properties tab currently presents a metamodel URI combo box, but we've been trying to get away from EMF. The New Model wizard displays only the simple Model Class and Model Type values. We'd of course, limit the Model Classes to Relational, XML Document, Web Services and Function models. Model types would be Source, View and in the case of Function model, "User Defined Function" model type. Without the Model Type selection, which is currently missing, users won't be able to target or limit applying properties to specific model types. The REST extension properties, for instance is only applicable to "View" models. It's MED should include supported Model Types list to include only View + Relational. We probably need to allow a third Relational model type of "BOTH", so an MED wouldn't have to be created for both metamodels? -- 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

4
5
0 / 0

[JBoss JIRA] (TEIIDDES-1187) Add MED Editor's Overview info as a second page in the New MED wizard

by Barry LaFond (Created) (JIRA)

Add MED Editor's Overview info as a second page in the New MED wizard --------------------------------------------------------------------- Key: TEIIDDES-1187 URL: https://issues.jboss.org/browse/TEIIDDES-1187 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Reporter: Barry LaFond Fix For: 7.7 While adding docs to 7.6 MED framework, and working with the "New" wizard, it seems that we could add a second page which included the Namespace URI, extended Model type, Description, etc. Creating an Empty MED is really no different than the "New > File" wizard. Let's add another page and put some meat in this thing. -- 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

5
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-676) Add good defaults to XML Schema Import Wizard

by John Verhaeg (JIRA)

Add good defaults to XML Schema Import Wizard --------------------------------------------- Key: TEIIDDES-676 URL: https://jira.jboss.org/browse/TEIIDDES-676 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.1 Reporter: John Verhaeg We should choose good defaults throughout this wizard, such as: - Pre-select the "from file system" option (vs. "via URL") on the first page - Auto-populate the "From directory" field to the user folder and remember whatever the user finally chooses thereafter. Working with a selection dialog that only allows you to choose a folder is too different from the norm to not be awkward. Always takes me a few seconds to remember why the *file* I'm trying to select is grayed-out. - Auto-populate the "Into folder" field if there is only one folder, a single project folder, in the workspace. - Provide a way to create a project so the user doesn't have to exit the entire wizard if they forget to first do that. -- 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

14 years, 3 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2011