January 2010 - 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, 1 month

5
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-220) New Model Wizard prefs for XML Doc Model not getting picked up.

by Mark Drilling (JIRA)

New Model Wizard prefs for XML Doc Model not getting picked up. --------------------------------------------------------------- Key: TEIIDDES-220 URL: https://jira.jboss.org/jira/browse/TEIIDDES-220 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 6.0.0, 6.1.0, 6.2.0, Future Reporter: Mark Drilling Assignee: Mark Drilling Priority: Minor The mapping class generation preference is being saved, but is not being picked up correctly on relaunch of the New Model wizard. This results in the xml doc model potentially being generated with the incorrect mapping class generator preference. -- 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, 3 months

2
13
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-257) enhancement to provide better visibility to Request parameters from within the Response document

by Debbie Steigner (JIRA)

enhancement to provide better visibility to Request parameters from within the Response document ------------------------------------------------------------------------------------------------ Key: TEIIDDES-257 URL: https://jira.jboss.org/jira/browse/TEIIDDES-257 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 7.0 Reporter: Debbie Steigner Fix For: 7.0 Need a way to pass WS request inputs to an XML response doc that doesn't include them in the response. Requesting an enhancement to provide better visibility to Request parameters from within the Response document. One logical way to do that is to expose them in the Input Set of each mapping class in the Response. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-247) Salesforce Connector returns a blank error message box when running the getupdated procedure

by Debbie Steigner (JIRA)

Salesforce Connector returns a blank error message box when running the getupdated procedure -------------------------------------------------------------------------------------------- Key: TEIIDDES-247 URL: https://jira.jboss.org/jira/browse/TEIIDDES-247 Project: Teiid Designer Issue Type: Bug Reporter: Debbie Steigner Fix For: Future If you execute the Salesforce getupdated procedure with a date range that returns an empty result set, instead of an empty result set you get an empty error message window and the following error in the log : !STACK 1 ConnectorException: Status ERROR: com.metamatrix.core code=0 null at com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated(SalesforceConnection.java:737) at com.metamatrix.connector.salesforce.execution.GetUpdatedExecutionImpl.execute(GetUpdatedExecutionImpl.java:65) at com.metamatrix.connector.salesforce.execution.ProcedureExecutionParentImpl.execute(ProcedureExecutionParentImpl.java:86) at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:300) at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processBatchRequest(ConnectorWorker.java:165) at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:139) at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- 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, 7 months

3
3
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2010