February 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-801) "Create Teiid Data Source" Dialog Incorrectly Disallows Some Valid Characters for Name

by Ted Jones (JIRA)

"Create Teiid Data Source" Dialog Incorrectly Disallows Some Valid Characters for Name -------------------------------------------------------------------------------------- Key: TEIIDDES-801 URL: https://issues.jboss.org/browse/TEIIDDES-801 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 7.1.1 Reporter: Ted Jones Assignee: Barry LaFond I added some "-" characters for my data source name (and also tried ".") and I received an error saying, "Name is not valid. Name cannot contain any of the following characters: ; @ # $ % ^ & * ( ) [ ] { } = | ! < > ? \". Seems like all non-alpha-numeric characters are being disallowed which is not the expected behavior. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-817) Refactoring a source model left transformation with mix of old and new model names

by Paul Nittel (JIRA)

Refactoring a source model left transformation with mix of old and new model names ---------------------------------------------------------------------------------- Key: TEIIDDES-817 URL: https://issues.jboss.org/browse/TEIIDDES-817 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.3 Reporter: Paul Nittel I created a project containing a textfile model, a view model (EatsText) which depends on the textfile model. I then stacked another model (UsesText) on top and added a concat sequence to make a fullname. Saved, executed and it looked good. Then, I refactored EatsTest to Employees and got a validation error in UsesText. When I looked at the transformation, here's what I found: SELECT EatsText.et.lastName, Employees.et.firstName, Employees.et.middleName, CONCAT2(EatsText.et.lastName, CONCAT2(', ', CONCAT2(EatsText.et.firstName, CONCAT2(' ', LEFT(EatsText.et.middleName, 1))))) AS FullName, Employees.et.empId, Employees.et.department, Employees.et.annualSalary, Employees.et.title, Employees.et.homePhone, Employees.et.mgrId, Employees.et.street, Employees.et.city, Employees.et.state, Employees.et.ZipCode FROM EatsText.et It has both the old and refactored names in it. Oddly, the SELECT contains both--I could see where the SELECT could be right and the FROM wrong. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
11
0 / 0

[JBoss JIRA] Created: (TEIIDDES-473) Incorporate Salesforce Importing Docs

by Steve Hawkins (JIRA)

Incorporate Salesforce Importing Docs ------------------------------------- Key: TEIIDDES-473 URL: https://jira.jboss.org/browse/TEIIDDES-473 Project: Teiid Designer Issue Type: Task Components: Import/Export Affects Versions: 7.0 Reporter: Steve Hawkins Teiid previously contained a guide for the salesforce logic that contained both teiid and teiid designer related information. The teiid specific information is now in the reference. A home is needed for the rest. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-754) Testing Connection on already-connected server sets the error icon, even if connection is successful

by Mark Drilling (JIRA)

Testing Connection on already-connected server sets the error icon, even if connection is successful ---------------------------------------------------------------------------------------------------- Key: TEIIDDES-754 URL: https://issues.jboss.org/browse/TEIIDDES-754 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.1 Environment: linux Reporter: Mark Drilling In designer, I have a connected server instance. 1) Select the server instance, then Rt-Click 'Teiid Server properties' to pull up properties dialog 2) Click the 'Test' button to verify the server connection. When you do this, the server instance shows an error icon. 3) When you click finish, the server error icon is still there - even though the test was successful. (And you can still execute queries against it.) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[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, 2 months

2
7
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-822) Fully-qualified names should not be required when referencing procedures that have unique unqualified names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-822?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDDES-822: ------------------------------------ Attachment: TransformationMetadata.java.patch > Fully-qualified names should not be required when referencing procedures that have unique unqualified names > ----------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-822 > URL: https://issues.jboss.org/browse/TEIIDDES-822 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 7.0 > Reporter: Michael Walker > Assignee: Steven Hawkins > Priority: Minor > Fix For: 7.3 > > Attachments: TransformationMetadata.java.patch > > > This problem occurs in our transformation editor, and also occurs with real-time queries (e.g. from QueryBuilder/SQLExplorer, or any client). > If you reference a non-qualified table name, e.g. "myTable", in a query, we'll attempt to resolve it if it is a unique name. > Strangely, we don't do the same thing for virtual procedures, even if they are unique. Instead, you must use the fully-qualified name. There should be no disparity. This is a usability defect. > This also happens to greatly extend the size of virtual procedure code, making it harder to read and debug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-838) Refactoring a source model left transformation with mix of old and new model names

by Van Halbert (JIRA)

Refactoring a source model left transformation with mix of old and new model names ---------------------------------------------------------------------------------- Key: TEIIDDES-838 URL: https://issues.jboss.org/browse/TEIIDDES-838 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.3 Reporter: Paul Nittel Assignee: Barry LaFond Priority: Blocker Fix For: 7.3 I created a project containing a textfile model, a view model (EatsText) which depends on the textfile model. I then stacked another model (UsesText) on top and added a concat sequence to make a fullname. Saved, executed and it looked good. Then, I refactored EatsTest to Employees and got a validation error in UsesText. When I looked at the transformation, here's what I found: SELECT EatsText.et.lastName, Employees.et.firstName, Employees.et.middleName, CONCAT2(EatsText.et.lastName, CONCAT2(', ', CONCAT2(EatsText.et.firstName, CONCAT2(' ', LEFT(EatsText.et.middleName, 1))))) AS FullName, Employees.et.empId, Employees.et.department, Employees.et.annualSalary, Employees.et.title, Employees.et.homePhone, Employees.et.mgrId, Employees.et.street, Employees.et.city, Employees.et.state, Employees.et.ZipCode FROM EatsText.et It has both the old and refactored names in it. Oddly, the SELECT contains both--I could see where the SELECT could be right and the FROM wrong. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-821) Remove UML2 and Relationship metamodels from New Model wizard options.

by Barry LaFond (JIRA)

Remove UML2 and Relationship metamodels from New Model wizard options. ---------------------------------------------------------------------- Key: TEIIDDES-821 URL: https://issues.jboss.org/browse/TEIIDDES-821 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.2, 7.1.1 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.3 UML2 and Relationship metamodels are immature and not part of long-term support plan. Need to remove them as New Model metamodel options. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-781) CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-781?page=com.atlassian.jira.plug... ] John Doyle resolved TEIIDDES-781. --------------------------------- Fix Version/s: 7.3 (was: 7.2) Resolution: Done Updated model generation. > CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure. > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-781 > URL: https://issues.jboss.org/browse/TEIIDDES-781 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.1.1, 7.2 > Reporter: John Doyle > Assignee: John Doyle > Priority: Critical > Fix For: 7.3, 7.1.1 > > Attachments: flat-file-procedures-option.png, flat_file_procedures.png, ForBarryTeiiddes-781.zip, generate-flat-file-procedures-page.png, invoke.jpg, invokeHttp.jpg, Teiiddes-781.patch, TEIIDDES-781.patch.txt, TEIIDDES_781_org.teiid.designer.relational.ui.patch > > > If a user models a SOAP service defined by a WSDL using the WSDL to Relational Model importer, the importer creates the invoke() physical procedure for the user. The execute procedure is required to execute the translator/connector. > If the service is not defined by a WSDL (ie. REST service, XML RPC service, ...), or is File based, then the user currently has to go through the error prone process of creating the physical models that define the procedures for the File and WS translators. Since the declaration of these procedures is static and known, JBDS/Teiid Designer should create the models for the user. > For the File Translator we should define getFiles, getTextFiles, and saveFile. > For the WS Translator we should define invoke and invokeHttp. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-685) XML-Relational models should be flagged as invalid in Teiid Designer 7.X

by John Doyle (JIRA)

XML-Relational models should be flagged as invalid in Teiid Designer 7.X ------------------------------------------------------------------------ Key: TEIIDDES-685 URL: https://jira.jboss.org/browse/TEIIDDES-685 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.1, 7.0 Reporter: John Doyle Assignee: John Doyle The XML-Relational connectors were removed from Teiid and therefore the XML-Relational models are no longer valid artifacts. For model projects created in earlier versions of Designer with XML-Relational models, we should recognize those models (through their model extensions) and flag them as invalid. The message should provide the user with a pointer to the new way to integrate with xml/web services. -- 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, 2 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 February 2011