February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-180) Consider using Salesforce retrieve() rather than generic query() call for queries with IN criteria

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-180?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-180: ------------------------------- Component/s: Salesforce Connector Fix Version/s: 6.x Affects Version/s: 6.x > Consider using Salesforce retrieve() rather than generic query() call for queries with IN criteria > -------------------------------------------------------------------------------------------------- > > Key: TEIID-180 > URL: https://jira.jboss.org/jira/browse/TEIID-180 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.x > Environment: MM 5.5.2 patch 0037/SFDC GA connector > Reporter: Greg Haber > Assignee: John Doyle > Fix For: 6.x > > > One of the usage guidelines for the SFDC WS API (http://blog.sforce.com/sforce/2005/04/performance_tip.html) says > Get familiar with the retrieve call. If you are pulling data from related tables, the retrieve call is a high performance call that you should be using > So I looked up retrieve() in the API doc (http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_...) > It looks like retrieve() is a special purpose call that gives high performance when you want to retrieve a list of records from an object by object Id. It lets you select which fields you want returned (and I believe their order), but does not allow any functions on those fields, or any additional criteria beyond this object list. > At first, this sounds like a very limited case, but in fact this is essentially the case we have in the SFDC connector when MM plans out a query as a dep join, with an SFDC table as the dependent source. In fact the API doc specifically recommends retrieve() for this case: > Client applications can use retrieve() to perform a client-side join. For example, a client application can run a query() to obtain a set of Opportunity records, iterate through the returned opportunity records, obtain the accountId for each opportunity, and then call retrieve() to obtain Account information for those accountIds. > We may want to implement this special case in the SFDC connector - if a query has as criteria only a single IN clause, and that IN clause is on the Id column, then use retrieve rather than query. > If we implement relationship joins in the SFDC connector, then this optimization is largely irrelevant - so this is a potential fallback or stopgap if we don't want to tackle relationship joins just yet. -- 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-177) Provide JDBC 1.5 backwards compatibility

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-177?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-177: ------------------------------- Component/s: JDBC Driver Fix Version/s: 6.1.0 Affects Version/s: 6.x > Provide JDBC 1.5 backwards compatibility > ---------------------------------------- > > Key: TEIID-177 > URL: https://jira.jboss.org/jira/browse/TEIID-177 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 6.1.0 > > > The jdbc driver needs to support jdk 1.5 on the client. -- 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-178) Implement sort minimization in process plans

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-178?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-178: ------------------------------- Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.x > Implement sort minimization in process plans > -------------------------------------------- > > Key: TEIID-178 > URL: https://jira.jboss.org/jira/browse/TEIID-178 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Sorting for order bys, dub removal, merge joins, and grouping should be minimized after the process plan has been determined. -- 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-174) add support to MMCallableStatement for named parameter methods

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-174?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-174: ------------------------------- Component/s: JDBC Driver Fix Version/s: 7.x Affects Version/s: 6.x > add support to MMCallableStatement for named parameter methods > -------------------------------------------------------------- > > Key: TEIID-174 > URL: https://jira.jboss.org/jira/browse/TEIID-174 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.x > > > Defect Tracker #20152: Now that we support named parameters for procedure, we should implement the setter methods in CallableStatement having to do with named parameters. > Be sure to update the list of Unsupported Methods in our JDBC driver, wherever that list is. Last report, it was sent to Warren to be added as an appendix to some documentation. -- 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-175) Asynchronous union results

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-175?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-175: ------------------------------- Component/s: Query Engine Affects Version/s: 6.1.0 > Asynchronous union results > -------------------------- > > Key: TEIID-175 > URL: https://jira.jboss.org/jira/browse/TEIID-175 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.1.0 > Reporter: Marc Shirley > Priority: Optional > Original Estimate: 3 days > Remaining Estimate: 3 days > > This is really a request for a dup-removal algorithm that can return results without waiting for all results. This would be generally less efficient than the full-sort approach, so it would be good to base the decision on a hint or costing information. -- 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-176) Auto-Staging tables should be shared in some circumstances

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-176?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-176: ------------------------------- Component/s: XML Planner/Processor Fix Version/s: 7.x Affects Version/s: 6.x > Auto-Staging tables should be shared in some circumstances > ---------------------------------------------------------- > > Key: TEIID-176 > URL: https://jira.jboss.org/jira/browse/TEIID-176 > Project: Teiid > Issue Type: Feature Request > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.x > > > Defect Tracker #24699: Auto-staging tables at least for shared sibling mapping classes will potentially be redundant. It would be good to detect similar root queries in determining a minimal set of staging tables. -- 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-173) ProductAdmin role can deploy a vdb but cannot create connector bindings

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-173?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-173: ------------------------------- Component/s: Query Engine Server Fix Version/s: 6.1.0 Affects Version/s: 6.x > ProductAdmin role can deploy a vdb but cannot create connector bindings > ----------------------------------------------------------------------- > > Key: TEIID-173 > URL: https://jira.jboss.org/jira/browse/TEIID-173 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.x > Reporter: Steve Jacobs > Fix For: 6.1.0 > > > Defect Tracker #24544: Seems like if I have authorization to deploy a VDB, I should have authorization to create connector bindings. This should be re-evaluated. -- 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-170) Fully implement joining of parent and child mapping classes

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-170?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-170: ------------------------------- Component/s: XML Planner/Processor Fix Version/s: 7.x Affects Version/s: 6.x > Fully implement joining of parent and child mapping classes > ----------------------------------------------------------- > > Key: TEIID-170 > URL: https://jira.jboss.org/jira/browse/TEIID-170 > Project: Teiid > Issue Type: Feature Request > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 7.x > > > Defect Tracker #24384: There is experimental code for joining parent and child mapping classes (as well as unioning sibling queries together) in JoinSourceNodes. However it needs to be refined and tested fully. It should probably be reimplemented so that siblings are joined, not unioned together however due to large result sets this can produce, it would be best to wait for fragments (which should have explicit relationships between parent and child) to take this route. -- 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-171) Add SQLXML Function for Extract()

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-171?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-171: ------------------------------- Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > Add SQLXML Function for Extract() > --------------------------------- > > Key: TEIID-171 > URL: https://jira.jboss.org/jira/browse/TEIID-171 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > We had a posting on the dev site (http://devcentral.metamatrix.com/node/2089809383) asking how they can retrieve an entire xml node from an input doc in a web service transformation instead of just the node text. Our current xPath function xPathValue() always return the text. We need something more like SQLXML extract()/extractvalue() so we can return the xml OR the text. -- 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-168) Remove resultset caching

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-168: ------------------------------- Component/s: JDBC Connector Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.x > Remove resultset caching > ------------------------ > > Key: TEIID-168 > URL: https://jira.jboss.org/jira/browse/TEIID-168 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector, Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Resultset caching should be replaced with relation and procedure caching. This would initially be backed by the buffermanager, based upon hints/costing, and be utilized by the planner rather than the resolver. It would be good if we also detected the level of determinism. -- 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