teiid-issues August 2009

teiid-issues@lists.jboss.org

1 participants
204 discussions

[JBoss JIRA] Updated: (TEIID-308) Merge the query rewriter and expression evaluator visitor

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-308?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-308: --------------------------------- Description: The query rewriter, expression evaluator visitor, and visitors (CorrelatedVariableSubstitutionVisitor, VariableSubstituionVisitor) used only during rewrite should be merged to run together. The query rewriter needs to be made stateful to do this. was: The query rewriter and expression evaluator visitor need to be run together and should be merged to a single class, but the query rewriter needs to be made stateful to do this. Priority: Minor (was: Optional) > Merge the query rewriter and expression evaluator visitor > --------------------------------------------------------- > > Key: TEIID-308 > URL: https://jira.jboss.org/jira/browse/TEIID-308 > Project: Teiid > Issue Type: Task > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The query rewriter, expression evaluator visitor, and visitors (CorrelatedVariableSubstitutionVisitor, VariableSubstituionVisitor) used only during rewrite should be merged to run together. The query rewriter needs to be made stateful to do this. -- 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

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-308) Merge the query rewriter and expression evaluator visitor

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-308?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-308: --------------------------------- Fix Version/s: 6.2.0 (was: 6.x) > Merge the query rewriter and expression evaluator visitor > --------------------------------------------------------- > > Key: TEIID-308 > URL: https://jira.jboss.org/jira/browse/TEIID-308 > Project: Teiid > Issue Type: Task > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.2.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The query rewriter and expression evaluator visitor need to be run together and should be merged to a single class, but the query rewriter needs to be made stateful to do this. -- 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

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Work started: (TEIID-202) Salesforce connector should support SOQL Relationship Queries

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-202?page=com.atlassian.jira.plug... ] Work on TEIID-202 started by John Doyle. > Salesforce connector should support SOQL Relationship Queries > ------------------------------------------------------------- > > Key: TEIID-202 > URL: https://jira.jboss.org/jira/browse/TEIID-202 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: Greg Haber > Assignee: John Doyle > Fix For: 6.2.0 > > > [from loleary mail on 05-23-2008] > Looking at version 8.0 of the sforce API, it seems that SOQL supports > relationship queries. Although these are not JOIN queries, they > function in the same manner as long as the objects in question have a > relationship to the object being queried (i.e. primary/foreign keys). > The document explaining the syntax can be found at: > http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_... > [ghaber] If the salesforce connector had the ability to do relationship queries, it would be a big impact on performance accessing SFDC, given the high per-query cost of accessing SFDC, which makes doing the joins in MM (planned as dependent joins) fairly slow in Genentech's beta testing of the connector. > Since relationship joins require that the join be a LOJ or ROJ only, and further require that the join criteria be PK-FK relationships only, it would be best if these limitations could be reflected in capabilities - see JBEDSP-58 (and my comment on it specifically about Salesforce) for discussion of the desired capabilities API enhancements. > I believe that it is worthwhile to implement relationship joins even without resolution of JBEDSP-58, with joins that cannot be pushed down throwing an exception. You'd also want to have a connector binding property that enabled/disabled this relationship query support (with the join methods in the Capabilities interface returning true if this property is set to enabled and false if set to disabled), so that the SFDC connector could still be used in other join scenarios if necessary. -- 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

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Work started: (TEIID-209) SalesForce Connector should support semi-join and anti-join pushdown upon release of 14.0 API

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-209?page=com.atlassian.jira.plug... ] Work on TEIID-209 started by John Doyle. > SalesForce Connector should support semi-join and anti-join pushdown upon release of 14.0 API > --------------------------------------------------------------------------------------------- > > Key: TEIID-209 > URL: https://jira.jboss.org/jira/browse/TEIID-209 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: John Doyle > Fix For: 6.2.0 > > > SalesForce API 14.0 is adding support for semi-joins and anti-joins, e.g.: > SELECT Id, Name > FROM Account > WHERE Id IN > (SELECT AccountId FROM Opportunity WHERE StageName = 'Closed Lost') > Supporting pushdown in these situations could improve query performance dramatically in some cases. > It appears that the API puts a number of odd restrictions on the use of these "joins", which may make the implementation difficult. > See http://www.salesforce.com/us/developer/docs/api/index.htm for details (search the index for SOQL select). -- 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

14 years, 9 months

1
0
0 / 0

← Newer
1
...
18
19
20
21
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2009