August 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-177) Provide JDBC 3.0 JRE 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: ------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Moving to 6.3, as there is no real requirement to finish this in 6.2 > Provide JDBC 3.0 JRE 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: 7.x > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 6.3.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, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-400) SOAP Relational connector throws org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-400?page=com.atlassian.jira.plug... ] John Doyle closed TEIID-400. ---------------------------- Fix Version/s: (was: 6.2.0) Resolution: Won't Fix This issue no longer reproduces in the current connector. The implementation has changed. > SOAP Relational connector throws org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR > ----------------------------------------------------------------------------- > > Key: TEIID-400 > URL: https://jira.jboss.org/jira/browse/TEIID-400 > Project: Teiid > Issue Type: Bug > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: John Doyle > > When executing a SOAP service and passing an empty SOAP body, the following exception is thrown. > org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (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... ] John Doyle resolved TEIID-209. ------------------------------ Resolution: Done Revision 1267. > 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

15 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (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... ] John Doyle resolved TEIID-202. ------------------------------ Resolution: Done Revision 1267. > 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

15 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-216) Query timeout should be enforced by the server

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-216?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-216: --------------------------------- Fix Version/s: 6.3.0 (was: 7.0) > Query timeout should be enforced by the server > ---------------------------------------------- > > Key: TEIID-216 > URL: https://jira.jboss.org/jira/browse/TEIID-216 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.3.0 > > > Defect Tracker #4990 : Query timeouts should be enforced by the server and client. > Also the RelationalNode nextbatch method will need to be made aware of the timeslice/timeout when handling 0 length batches. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-321) Refactor symbol language objects

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-321?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-321: --------------------------------- Fix Version/s: 7.0 (was: 6.3.0) > Refactor symbol language objects > -------------------------------- > > Key: TEIID-321 > URL: https://jira.jboss.org/jira/browse/TEIID-321 > Project: Teiid > Issue Type: Task > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Defect Tracker #25035: The current structuring of Symbol objects is confusing and makes planning more difficult than necessary. Changes that should be made: > AggregateSymbol should become AggregateFunction (which should not inherit from Function) and not be a Symbol. > SingleElementSymbol, ExpressionSymbol, and AliasSymbol should be merged to a single class DerivedSymbol > DerivedSymbol and MultipleElementSymbol should implement SelectSymbol (as an interface rather than base class) and SelectSymbol should provide a method for getting the projected symbols. > ElementSymbol should not directly be a DerivedSymbol. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-216) Query timeout should be enforced by the server

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-216?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-216: --------------------------------- Fix Version/s: 7.0 (was: 6.3.0) > Query timeout should be enforced by the server > ---------------------------------------------- > > Key: TEIID-216 > URL: https://jira.jboss.org/jira/browse/TEIID-216 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 7.0 > > > Defect Tracker #4990 : Query timeouts should be enforced by the server and client. > Also the RelationalNode nextbatch method will need to be made aware of the timeslice/timeout when handling 0 length batches. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-303) Remove the LanguageBridgeFactory

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-303?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-303: --------------------------------- Fix Version/s: 7.0 (was: 6.3.0) > Remove the LanguageBridgeFactory > -------------------------------- > > Key: TEIID-303 > URL: https://jira.jboss.org/jira/browse/TEIID-303 > Project: Teiid > Issue Type: Task > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > > Defect Tracker #25061: The language objects at the data layer are redundent with the language objects used in commands. The LanguageBridgeFactory can be removed in favor of simply cloning and issuing a command. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-500) Request for INSERT INTO...SELECT..FROM capability for virtual tables

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-500?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-500. ---------------------------------- Resolution: Done Added support using the plantoprocessconverter - since we currently rewrite insert with a query expression as a select into. Will create an issue for changing the internal processing model to insert all the way. > Request for INSERT INTO...SELECT..FROM capability for virtual tables > -------------------------------------------------------------------- > > Key: TEIID-500 > URL: https://jira.jboss.org/jira/browse/TEIID-500 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 6.2.0 > > > Per Issue Tracker ticket https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... . requesting the capability to use the INSERT INTO.. SELECT ..FROM syntax on virtual tables. > If this cannot be done, can a change be made to the SQL Validation to throw an exception. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-250) Enable Axis data compression in SFDC Connector, per SFDC API guidelines

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-250?page=com.atlassian.jira.plug... ] John Doyle updated TEIID-250: ----------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) > Enable Axis data compression in SFDC Connector, per SFDC API guidelines > ----------------------------------------------------------------------- > > Key: TEIID-250 > URL: https://jira.jboss.org/jira/browse/TEIID-250 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0 > Environment: MetaMatrix 5.5.2 with patch 0037/SFDC GA connector > Reporter: Greg Haber > Assignee: John Doyle > Fix For: 6.3.0 > > > The SFDC doc includes a set of performance guidelines for using their API (http://blog.sforce.com/sforce/2005/04/performance_tip.html). One of the guidelines: > Use compression, unless you have an OC45 connection into the back of your machine, compression will help reduce transmission times, the Sforce API supports gzip and deflate compression for both request and response. > does not look like it has been implemented in our connector. In theory, this will be a big optimization when returning large data sets, as is the case at Genentech. This is also a trivial optimization to implement, so we should at least try this out and see what the impact is. > The process for enabling this is described on http://wiki.apexdevnet.com/index.php/Compression_with_Axis_1.3 - essentially, you subclass the SforceServiceLocator class in the salesforce.jar to set a few Axis-specific properties (complete code for subclass is at the link), and then in our connector (in ConnectionImpl) we call this subclass instead of calling the SforceServiceLocator directly, as we are doing today. > This is a very low hanging fruit with a big upside - please implement soon. -- 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, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2009