July 2009 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-216) Designer removes parentheses around criteria in ansi join when using compound ON

by Marc Shirley (JIRA)

Designer removes parentheses around criteria in ansi join when using compound ON -------------------------------------------------------------------------------- Key: TEIIDDES-216 URL: https://jira.jboss.org/jira/browse/TEIIDDES-216 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.1.0 Reporter: Marc Shirley In Designer, when validating a transformation that has compound criteria in an ansi join statement's ON, the parentheses are removed and the order of operations is modified as a result. This does not appear to occur when using the same parentheses structure in WHERE criteria. Before validation: SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON (a.INTKEY = b.INTKEY) AND (a.INTNUM IS NULL OR a.INTNUM = 11) After validation: SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON a.INTKEY = b.INTKEY AND (a.INTNUM IS NULL) OR (a.INTNUM = 11) After validating a second time: SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON ((a.INTKEY = b.INTKEY) AND (a.INTNUM IS NULL)) OR (a.INTNUM = 11) -- 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

12 years, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-122) Add WSDL 2.0 Support to Designer for Data Services

by Ted Jones (JIRA)

Add WSDL 2.0 Support to Designer for Data Services -------------------------------------------------- Key: TEIIDDES-122 URL: https://jira.jboss.org/jira/browse/TEIIDDES-122 Project: Teiid Designer Issue Type: Feature Request Affects Versions: 6.0.0 Reporter: Ted Jones Fix For: 6.0.0 In order to support REST (see TEIID-417), we need to allow for the generation of WSDL 2.0 specific WSDL. We still need to allow for the generation of WSDL 1.1 since WSDL 2.0 is not widely supported by many tools. There should be an option in the Designer to specify which version of the WSDL specification to use when generating the WSDL file. I suggest putting the option on the Web Services tab of the VDB, but I am open for other suggestions. Alternatively, we could add the WSDL using both specifications in separate WSDL files and then provide a different WSDL URL to get one or the other. This approach seems like overkill to me though and would have farther reaching ramifications. Ideally this would be completed for Westport. -- 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

12 years, 4 months

2
12
0 / 0

[JBoss JIRA] Created: (TEIIDDES-152) Update the function model to support vararg functions

by Steven Hawkins (JIRA)

Update the function model to support vararg functions ----------------------------------------------------- Key: TEIIDDES-152 URL: https://jira.jboss.org/jira/browse/TEIIDDES-152 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.0.0 Reporter: Steven Hawkins Vararg support allows for functions with any number of parameters. It requires adding additional metadata to a parameter or function to indicate that the last parameter accepts any number of arguments of that type. -- 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

12 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.

by John Doyle (JIRA)

XML-Relaional modeling needs to be easier for sources that do not provide an XSD. --------------------------------------------------------------------------------- Key: TEIIDDES-119 URL: https://jira.jboss.org/jira/browse/TEIIDDES-119 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Reporter: John Doyle Assignee: John Doyle The main case for this is REST services. REST services do not have a standard description mechanism like WSDL for SOAP services. The inputs and outputs of the service might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand modeling is too difficult, so we need to come up with other assists. The solution is probably a mix of new features and documented best practices. For example: Add WADL support to the importer. Document use of a schema from XML tool (like inst2XSD) -- 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

12 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (TEIIDDES-175) Define a contract beween Teiid and Designer that enables Designer to use different versions of Teiid.

by John Doyle (JIRA)

Define a contract beween Teiid and Designer that enables Designer to use different versions of Teiid. ----------------------------------------------------------------------------------------------------- Key: TEIIDDES-175 URL: https://jira.jboss.org/jira/browse/TEIIDDES-175 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Reporter: John Doyle Teiid Designer should be able to execute models/VDBs with different versions of Teiid. In order to accomplish this in a user friendly manner, a contract should be agreed upon between Teiid and Designer. Designer could invoke Teiid via this contract and the user would be able to easily repoint Designer to different versions of Teiid in order to test models/VDBs across different 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

12 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-173) In-line rename not enabled for newly created Web Service Operation

by Barry LaFond (JIRA)

In-line rename not enabled for newly created Web Service Operation ------------------------------------------------------------------ Key: TEIIDDES-173 URL: https://jira.jboss.org/jira/browse/TEIIDDES-173 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Priority: Minor Fix For: Future 1) Open Web Service Model in Model Editor 2) Select Web Service Interface in Model explorer 3) Right-click select New > Child > Operation 4) New Operation shows up in Explorer, but auto-rename is not enabled. -- 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

12 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-113) Ability to create partial copy of a model with new model wizard

by Barry LaFond (JIRA)

Ability to create partial copy of a model with new model wizard --------------------------------------------------------------- Key: TEIIDDES-113 URL: https://jira.jboss.org/jira/browse/TEIIDDES-113 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.0 Reporter: Barry LaFond Need to be able to create a new model from existing model (copy) and weed-out unwanted model children. Designer 5.5.3 version contained this feature, but after further review, the design was incomplete and has resulted in multiple bugs. So, plan is to remove this feature for the 6.0.0 release and then re-design & implement for 6.1.0 -- 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

12 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-116) Add ability to perform partial copy model operations in new model wizard

by Barry LaFond (JIRA)

Add ability to perform partial copy model operations in new model wizard ------------------------------------------------------------------------ Key: TEIIDDES-116 URL: https://jira.jboss.org/jira/browse/TEIIDDES-116 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: 6.1.0 -- 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

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-191) XSD as Relational importer has problems with child elements with many parents

by Greg Haber (JIRA)

XSD as Relational importer has problems with child elements with many parents ----------------------------------------------------------------------------- Key: TEIIDDES-191 URL: https://jira.jboss.org/jira/browse/TEIIDDES-191 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: Teiid Designer 6.0.0 official (14 May 2009) release Reporter: Greg Haber Attachments: address.xsd, person.xsd, person2.xml, person2.xsd I've encountered a lot of problems with the Teiid Designer XML as Relational Importer (and with its legacy ancestor) dealing with importing XSDs where a child element has multiple parents. The importer currently treats all elements throughout the XSD that have the same name and type as the same, and so models that element(s) as a single table with multiple parents, if the number of parents is above a configurable number (currently defaults to 3). Which is all well and good in theory, but in practice it seems to hit a number of problems 1) During the import process, if the selection of document root elements is left at the default, not all needed tables are generated. See person.xsd example attached. 2) If all possible root elements are selected, it looks mostly right, but there are often extra elements in the child tables (again try with person.xsd). Plus, the tables don't actually work at runtime correctly (try using attached person2.xml as the data source - notice that you can only get to the spouse's father from Person, not to their own father). I've also attached some other example problem XSDs - person2.xsd, and address.xsd Now, in some cases a reasonable workaround is to up the number of allowed parents parameter, so that everything gets folded into a single table. But that isn't a general solution, as it doesn't work with things like person2.xsd. -- 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

12 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-166) Exceptions Displaying Just Deleted Function In Expression Builder

by Dan Florian (JIRA)

Exceptions Displaying Just Deleted Function In Expression Builder ----------------------------------------------------------------- Key: TEIIDDES-166 URL: https://jira.jboss.org/jira/browse/TEIIDDES-166 Project: Teiid Designer Issue Type: Bug Components: Modeling, Transformations Affects Versions: 6.0.0 Reporter: Dan Florian 1. In a transformation editor use a function from the UDF model. 2. Delete that same function from the UDF. 3. Save UDF model. This should do a automatic build. 4. Go back to transformation editor and put cursor in the reference to the deleted function. 5. Start the Expression Builder. 6. Get exceptions. -- 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, 5 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2009