September 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-631) Add REST Implementation for Generated Web Service War

by Ted Jones (JIRA)

Add REST Implementation for Generated Web Service War ----------------------------------------------------- Key: TEIIDDES-631 URL: https://jira.jboss.org/browse/TEIIDDES-631 Project: Teiid Designer Issue Type: Feature Request Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.2 Need to add an option to generate a REST implementation of the generated web service war -- 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

13 years, 6 months

2
19
0 / 0

[JBoss JIRA] Created: (TEIIDDES-466) WSDL Generation from Web Service Models Creates Extraneous Nodes

by Ted Jones (JIRA)

WSDL Generation from Web Service Models Creates Extraneous Nodes ---------------------------------------------------------------- Key: TEIIDDES-466 URL: https://jira.jboss.org/browse/TEIIDDES-466 Project: Teiid Designer Issue Type: Task Components: Modeling Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.0 Generated web service models from a Books VDB which creates operations for getBooks, getAuthors, getBooks_Authors, and getPublishers. A separate port type, binding and port is generated for each operation. Only one port type, binding and port is needed. We should get rid of the extraneous nodes and combine into one port type, binding and port. -- 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

13 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-640) Exporting a relational to ddl, and turned off the comments option did not eliminate the comments from the ddl file.

by Van Halbert (JIRA)

Exporting a relational to ddl, and turned off the comments option did not eliminate the comments from the ddl file. ------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-640 URL: https://jira.jboss.org/browse/TEIIDDES-640 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Van Halbert Priority: Minor Fix For: 7.1.1 Using the export option to DDL, and changed the option to remove comments from being put into the ddl file, did not work. All the comments appeared there. -- 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

13 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (TEIIDDES-518) DTP context menu options on Teiid tables should consider whether virtual model supports update.

by Ken Johnson (JIRA)

DTP context menu options on Teiid tables should consider whether virtual model supports update. ----------------------------------------------------------------------------------------------- Key: TEIIDDES-518 URL: https://jira.jboss.org/browse/TEIIDDES-518 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Environment: Teiid Designer 7.0 + JBoss Dev Studio 3.0.1GA Teiid 7.1 Alpha on EAP 5.1 RHEL 6, OpenJDK 1.6 Reporter: Ken Johnson In DTP, Context menu for Table contains several options under Data->(Edit, Load, Extract, Sample Contents). For virtual tables, Extract and Sample Contents are fine. Edit and Load will attempt to write data. Thus a few issues: a) These options should be disabled if the table in question does not have Supports Update checked. b) These options should be tested when the table *does* have Update and Insert procedures defined. c) Tables in SYS schema should never be writable. When working with physical tables, all options should be available and work correctly. Cursory testing indicates this is the case - at least with a MySQL data source underlying the model. -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-268) "Create Web Service" wizard on a virtual procedure produces invalid SQL in transformation

by Debbie Steigner (JIRA)

"Create Web Service" wizard on a virtual procedure produces invalid SQL in transformation ----------------------------------------------------------------------------------------- Key: TEIIDDES-268 URL: https://jira.jboss.org/jira/browse/TEIIDDES-268 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.0 Reporter: Debbie Steigner Fix For: 7.0 If you use our "Create Web Service" wizard on a virtual procedure the SQL transformation for the Output View is invalid for the current product. For example, our wizard produced: SELECT * FROM (EXEC TwoStepsFeatureTable.TwoSteps(left_node = left_node)) AS TwoSteps so it errors on left_node: Resolver Error: Symbol left_node is specified with an unknown group context The transformation should be procedural relational instead: SELECT * FROM TwoStepsFeatureTable.TwoSteps -- 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

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-210) Add implicit conversion of NULL to correct datatype in transformation validator

by Marc Shirley (JIRA)

Add implicit conversion of NULL to correct datatype in transformation validator ------------------------------------------------------------------------------- Key: TEIIDDES-210 URL: https://jira.jboss.org/jira/browse/TEIIDDES-210 Project: Teiid Designer Issue Type: Feature Request Components: Transformations, Validation Affects Versions: 6.0.0, 6.1.0 Reporter: Marc Shirley When using NULL value as a column (ie, NULL as columnName), it is only implicitly converted to a string. When trying to use the NULL as a column of type date, integer, float, etc., the validator throws a warning that the transformation is not valid. If you wrap the NULL in a convert to the correct column datatype (ie, "convert(NULL,date)"), the transformation can be validated successfully. -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-188) Database Schema not used in sql query

by Ben Truitt (JIRA)

Database Schema not used in sql query ------------------------------------- Key: TEIIDDES-188 URL: https://jira.jboss.org/jira/browse/TEIIDDES-188 Project: Teiid Designer Issue Type: Bug Environment: Ubuntu 9.x eclipse 3.4.2 teiid_designer_6.0.0.v20090427_SNAPSHOT Postgresql 8.2 postgresql-8.3-604.jdbc4.jar Reporter: Ben Truitt It looks like the database schema specified in the XMI file for the model is not being used when generating the SQL query to preview data from the model. I'm attaching my model XMI file. Note the schema is named "rollback". However, the SQL query generated does not include the schema name, instead it only includes the table name. -- 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

13 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-304) External metadata needs to be marked as scalar groups where appropriate

by Van Halbert (JIRA)

External metadata needs to be marked as scalar groups where appropriate ----------------------------------------------------------------------- Key: TEIIDDES-304 URL: https://jira.jboss.org/jira/browse/TEIIDDES-304 Project: Teiid Designer Issue Type: Task Components: Modeling Reporter: Van Halbert Priority: Minor Fix For: 7.1 External temp metadata supplied by the designer should be marked as coming from a scalar group for INPUT, CHANGING, and VARIABLES groups. -- 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

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-570) Valid names can have almost any character, except periods. No periods!

by Paul Nittel (JIRA)

Valid names can have almost any character, except periods. No periods! ---------------------------------------------------------------------- Key: TEIIDDES-570 URL: https://jira.jboss.org/browse/TEIIDDES-570 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.1 Environment: All Reporter: Paul Nittel This SQL: SELECT t.* FROM (EXEC WeatherData.invoke(action = 'GET', endpoint = QUERYSTRING('', '38.99,-77.02 39.70,-104.80 47.6,-122.30' AS listLatLon, 'time-series' AS product, '2004-01-01T00:00:00' AS "begin", '2013-04-20T00:00:00' AS "end", 'maxt' AS maxt, 'mint' AS mint))) AS w, XMLTABLE('/dwml/data/location' PASSING result COLUMNS "location-key" string, lattitude string PATH 'point/@latitude', longitude string PATH 'point/@longitude') AS t will fail as location-key contains a hyphen. Actually, the only character which is not valid in a name is the period. Please verify with the Teiid server crew, but we should loosen up the validation criteria as appropriate. -- 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

13 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-574) Datatypes editor: Changing name of datatype is not reflected in list "Datatypes in <your>.xsd"

by Paul Nittel (JIRA)

Datatypes editor: Changing name of datatype is not reflected in list "Datatypes in <your>.xsd" ---------------------------------------------------------------------------------------------- Key: TEIIDDES-574 URL: https://jira.jboss.org/browse/TEIIDDES-574 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7.1M2 Reporter: Paul Nittel Priority: Minor While testing the simple datatypes editor we change the name of a datatype from PublicationYear to Temporary. When the change is made, the old name remains on the list of "Datatypes in BookDatatypes.xsd". Only after restarting the editor is the change noted in that list. Not a major issue, but it leaves the not-quite-finished impression. Reproduction steps are below. -- 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

13 years, 10 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2010