February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-219?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-219: --------------------------------- Actually this is not as easy as it seems our overall cost calculation is targeted only at cardinality, not in terms of a computational or time based estimate (that happens only for joins). We need to have a better representation of cost for this to be a meaningful constraint. > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://jira.jboss.org/jira/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 6.1.0 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-219?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-219: --------------------------------- Component/s: Query Engine Server Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://jira.jboss.org/jira/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 6.1.0 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-151) ENHANCEMENT: Need a way to stop building node in a recursive XML document when the node is repeated

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-151?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-151: ------------------------------- Component/s: XML Planner/Processor Fix Version/s: 7.x Affects Version/s: 6.x > ENHANCEMENT: Need a way to stop building node in a recursive XML document when the node is repeated > --------------------------------------------------------------------------------------------------- > > Key: TEIID-151 > URL: https://jira.jboss.org/jira/browse/TEIID-151 > Project: Teiid > Issue Type: Feature Request > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Li Liang > Fix For: 7.x > > > Defect Tracker #24234: When doing dependency analysis for MMR and output recursive xml document, it is possible that a child node depends on its parent node, or the parent of the parent node, etc. We need to be able to specify whether to stop in that case regardless of the recursion depth. > 1. Add a check box in recursion editor in modeler to specify whether to stop when node is repeated. > 2. Add logic in server to handle it. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-220) There should also be a value set property to proc inputs

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-220?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-220: --------------------------------- Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.0.0 This needs a corresponding designer enhancement. > There should also be a value set property to proc inputs > -------------------------------------------------------- > > Key: TEIID-220 > URL: https://jira.jboss.org/jira/browse/TEIID-220 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.x > > > Defect Tracker #24821: It would be useful to support specifying the full domain of values for procedure inputs. This would allow for the procedure to be invoked relationally without the use of a where clause. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-221) WS-RM Support in Enterprise Web Services

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-221?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-221: --------------------------------- Component/s: SOAP Services Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > WS-RM Support in Enterprise Web Services > ---------------------------------------- > > Key: TEIID-221 > URL: https://jira.jboss.org/jira/browse/TEIID-221 > Project: Teiid > Issue Type: Feature Request > Components: SOAP Services > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Priority: Minor > Fix For: 6.1.0 > > > Defect Tracker #24022: Need to test and document WS-RM with Axis2 in our Enterprise Web Services. Will require adding the Sandesha module to our distribution or documenting the steps on how to do this. ING is asking about our plans for WS-RM support in our roadmap, so we need to make sure this is done for 5.5/6.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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-147) Support for JAVA Stored Procedures

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-147?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-147: ------------------------------- Component/s: Query Engine Fix Version/s: 7.x Affects Version/s: 6.x > Support for JAVA Stored Procedures > ---------------------------------- > > Key: TEIID-147 > URL: https://jira.jboss.org/jira/browse/TEIID-147 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Ramesh Reddy > Fix For: 7.x > > > Currently the Stored procedure support is lacking for both our procedure language and XQuery. Procedure support could be extended to java (or groovy) code, which will provide a powerful engine to execute a arbitrary queries. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-148) Enhancement to allow runtime checking of null values

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-148?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-148: ------------------------------- Component/s: Query Engine Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Enhancement to allow runtime checking of null values > ---------------------------------------------------- > > Key: TEIID-148 > URL: https://jira.jboss.org/jira/browse/TEIID-148 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Environment: All server environments. > Reporter: Jerry Helbling > Assignee: Jerry Helbling > Priority: Minor > Fix For: 6.0.0 > > > Refer to internal case 6395. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-149) Add SOAP Header as Command Payload in Data Service

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-149?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-149: ------------------------------- Component/s: SOAP Services Fix Version/s: 6.x Affects Version/s: 6.x > Add SOAP Header as Command Payload in Data Service > -------------------------------------------------- > > Key: TEIID-149 > URL: https://jira.jboss.org/jira/browse/TEIID-149 > Project: Teiid > Issue Type: Feature Request > Components: SOAP Services > Affects Versions: 6.x > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.x > > > Defect Tracker #24883: We need to add any SOAP header values as a command payload to the statement executed in the data service. This will allow a custom MembershipSPI to access the header via the payload and do any special processing required. This would handle use cases such as SAML tokens, password digest decryption and authentication, and any other special cases the user may have. It is possible that the user may not want to pass any information to the payload so we may want to add setting (JVM arg, WSDL parm, etc.) to make this optional. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-150) Improve nested loop (in merge join) matching

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-150?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-150: ------------------------------- Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Improve nested loop (in merge join) matching > --------------------------------------------- > > Key: TEIID-150 > URL: https://jira.jboss.org/jira/browse/TEIID-150 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.x > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Nested loop evaluation should be based upon available blocks rather than fully iterating the inner side. The simplest approach is to just match a single block from the left and right at a time. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-142) Introduce a mechanism to allow single source updates without an xa txn.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-142?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-142: ------------------------------- Component/s: Query Engine Fix Version/s: 7.x Affects Version/s: 6.x > Introduce a mechanism to allow single source updates without an xa txn. > ----------------------------------------------------------------------- > > Key: TEIID-142 > URL: https://jira.jboss.org/jira/browse/TEIID-142 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.x > > > Defect Tracker #24910: txnAutoWrap = OFF in 5.5 disables the use of local transactions. This was primarily done to support customers who 1. weren't paying for the transactional product > 2. weren't using an XA connection for an update > The concern of 1 goes away in 5.6 as all customers will have a transactional product. The secondary concern requires either a connection property that either ignores autocommit or the generic support of 1 phase commit on connectors supporting update and local transactions. The latter solution would allow non-XA aware connectors to seem XA aware as long as all updates went to a single source. Arjuna would also need to be configured to support the one phase commit optimization. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009