February 2011 - teiid-designer-issues

[JBoss JIRA] Updated: (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 updated TEIIDDES-781: -------------------------------- Attachment: TEIIDDES-781.patch.txt Patch to change incorrect model creation. > 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.1.1, 7.2 > > 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (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 reopened TEIIDDES-781: --------------------------------- The generated model is not correct. > 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.1.1, 7.2 > > 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_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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-835) 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-835 URL: https://issues.jboss.org/browse/TEIIDDES-835 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-830) Importing MetaMatrix 5.5.4 project set does not bring in all the models correctly

by Van Halbert (JIRA)

Importing MetaMatrix 5.5.4 project set does not bring in all the models correctly --------------------------------------------------------------------------------- Key: TEIIDDES-830 URL: https://issues.jboss.org/browse/TEIIDDES-830 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.3 Reporter: Van Halbert Assignee: Barry LaFond Priority: Blocker Importing MetaMatrix 5.5.4 project set does not bring in all the models correctly. This was tried with the 5.5.4 .project and an updated .project with the Teiid Designer settings. Neither worked. However, was able to close the project and reopen, and the tables in the invalid model showed up (in both cases). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-829) Duplicate "Schema" name generated while creating XML transformations from XSD

by Ramesh Reddy (JIRA)

Duplicate "Schema" name generated while creating XML transformations from XSD ----------------------------------------------------------------------------- Key: TEIIDDES-829 URL: https://issues.jboss.org/browse/TEIIDDES-829 Project: Teiid Designer Issue Type: Bug Components: Transformations Environment: F14 JBDS-CR2 Reporter: Ramesh Reddy 1) Imported the Books.xsd, BookDataTypes.xsd 2) Open the Books, xml schema and select "bibilography" element 3) Right click "Modeling -> Create XML to Scalar Transformation" 4) That generates a procedure in a view model with schema name "bibiligraphy" 5) Right click "Modeling -> Create Scalar to XMl transformation" 6) That generates a another procedure in a view model with duplicate schema name "bibiligraphy" it should not even generate "schema" folder, just generate the procedure in the selected view model. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

CLONE - Remove UML2 and Relationship metamodels from New Model wizard options. ------------------------------------------------------------------------------ Key: TEIIDDES-828 URL: https://issues.jboss.org/browse/TEIIDDES-828 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.1.1, 7.2 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (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 moved TEIID-1462 to TEIIDDES-822: ------------------------------------------------ Project: Teiid Designer (was: Teiid) Key: TEIIDDES-822 (was: TEIID-1462) Issue Type: Feature Request (was: Bug) Affects Version/s: 7.0 (was: 7.0) Component/s: Modeling (was: Query Engine) Fix Version/s: 7.3 (was: 7.0) > 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 > > > 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-811) NPE while loading the example project

by Ramesh Reddy (JIRA)

NPE while loading the example project ------------------------------------- Key: TEIIDDES-811 URL: https://issues.jboss.org/browse/TEIIDDES-811 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Environment: JBDS Beta2 Reporter: Ramesh Reddy > java.lang.NullPointerException > at org.eclipse.ui.wizards.datatransfer.ImportOperation.importRecursivelyFrom(ImportOperation.java:789) > at org.eclipse.ui.wizards.datatransfer.ImportOperation.importFileSystemObjects(ImportOperation.java:674) > at org.eclipse.ui.wizards.datatransfer.ImportOperation.execute(ImportOperation.java:407) > at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) > at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) > at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard.importProject(NewProjectExamplesWizard.java:591) > at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard$2.runInWorkspace(NewProjectExamplesWizard.java:183) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-808) Provide the ability to name the Teiid instance for better reference in error messaging.

by Barry LaFond (JIRA)

Provide the ability to name the Teiid instance for better reference in error messaging. --------------------------------------------------------------------------------------- Key: TEIIDDES-808 URL: https://issues.jboss.org/browse/TEIIDDES-808 Project: Teiid Designer Issue Type: Enhancement Components: Teiid Integration, VDB & Execution Affects Versions: 7.2, 7.1.1 Reporter: Barry LaFond Assignee: Dan Florian Fix For: 7.3 Provide the ability to name the Teiid instance for better reference in error messaging. In jira TEIIDDES-283, when that is fixed, it would be good if it utilized the name of the Teiid instance in the error message. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-215) Autoincrement incorrectly imported for SQL Server 2008

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-215?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-215. ----------------------------------- Resolution: Done Added mods SQL Server relational model processor to handle "int identity" and other potential identity native types, strip the "identity" and set auto-increment. For the SQL Server DDL Export XSLT, Insured autoIncrement == TRUE was adding an "IDENTITY" field to the datatype. > Autoincrement incorrectly imported for SQL Server 2008 > ------------------------------------------------------ > > Key: TEIIDDES-215 > URL: https://issues.jboss.org/browse/TEIIDDES-215 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.1.0 > Environment: Windows XP, Eclipse 3.4.2, SQL Server 2008, JDBC driver by Microsoft > Reporter: Michael Riedmueller > Assignee: Barry LaFond > Fix For: 7.3 > > > Table attributes with type int and autoincrement set to true are imported with data type "int identity", autoincrement is NOT set in the properties. > This should be data type "int" and autoincrement set to true. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2011