July 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1099) Update Jopr Plugin to Use Long Running Query Property and Method on Teiid Engine

by Ted Jones (JIRA)

Update Jopr Plugin to Use Long Running Query Property and Method on Teiid Engine -------------------------------------------------------------------------------- Key: TEIID-1099 URL: https://jira.jboss.org/browse/TEIID-1099 Project: Teiid Issue Type: Task Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.0 Need to change the Jopr plugin logic to use the new LRQ property and method -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
2
0 / 0

[JBoss JIRA] Closed: (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/browse/TEIID-209?page=com.atlassian.jira.plugin.sy... ] John Doyle closed TEIID-209. ---------------------------- > SalesForce Connector should support semi-join and anti-join pushdown upon release of 14.0 API > --------------------------------------------------------------------------------------------- > > Key: TEIID-209 > URL: https://jira.jboss.org/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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-844) Implement metadata creation in the SalesForce connector.

by John Doyle (JIRA)

Implement metadata creation in the SalesForce connector. -------------------------------------------------------- Key: TEIID-844 URL: https://jira.jboss.org/jira/browse/TEIID-844 Project: Teiid Issue Type: Feature Request Components: Salesforce Connector Reporter: John Doyle Assignee: John Doyle Fix For: 6.3.0 The SF connector should use the new connector metadata API to produce it's own metadata. -- 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, 5 months

2
4
0 / 0

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

by John Doyle (JIRA)

[ https://jira.jboss.org/browse/TEIID-202?page=com.atlassian.jira.plugin.sy... ] John Doyle closed TEIID-202. ---------------------------- > Salesforce connector should support SOQL Relationship Queries > ------------------------------------------------------------- > > Key: TEIID-202 > URL: https://jira.jboss.org/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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

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

by John Doyle (JIRA)

[ https://jira.jboss.org/browse/TEIID-250?page=com.atlassian.jira.plugin.sy... ] John Doyle closed TEIID-250. ---------------------------- > Enable Axis data compression in SFDC Connector, per SFDC API guidelines > ----------------------------------------------------------------------- > > Key: TEIID-250 > URL: https://jira.jboss.org/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: 7.1 > > > 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

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

by John Doyle (JIRA)

[ https://jira.jboss.org/browse/TEIID-180?page=com.atlassian.jira.plugin.sy... ] John Doyle closed TEIID-180. ---------------------------- > Consider using Salesforce retrieve() rather than generic query() call for queries with IN criteria > -------------------------------------------------------------------------------------------------- > > Key: TEIID-180 > URL: https://jira.jboss.org/browse/TEIID-180 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0, 6.1.0, 6.2.0 > Environment: MM 5.5.2 patch 0037/SFDC GA connector > Reporter: Greg Haber > Assignee: John Doyle > Fix For: 7.0 > > > 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1149) Importing tables from a deployed VDB does not import columns

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1149?page=com.atlassian.jira.plugin.s... ] Steve Hawkins updated TEIID-1149: --------------------------------- Assignee: Steve Hawkins Fix Version/s: 7.1 Priority: Critical (was: Major) Component/s: Query Engine (was: JDBC Driver) > Importing tables from a deployed VDB does not import columns > ------------------------------------------------------------ > > Key: TEIID-1149 > URL: https://jira.jboss.org/browse/TEIID-1149 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final > Reporter: Paul Nittel > Assignee: Steve Hawkins > Priority: Critical > Fix For: 7.1 > > Attachments: NoColumns.png, TeiidDes-506Projects.zip > > > I created, and deployed, a VDB containing source and view models. I am able to query these tables. > I created a new project and into that project I attempted to import a view model's table from the previously-created VDB. What I found in the imported was the models and tables were shown, but no columns were available for import. Once imported, the tables did have no columns. > Screenshot and other stuff attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-1149) Importing tables from a deployed VDB does not import columns

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1149?page=com.atlassian.jira.plugin.s... ] Steve Hawkins commented on TEIID-1149: -------------------------------------- This is due to the use of the model based indexes. Previously each set of indexes included a copy of the datatype information. Now only the system metadata has a datatype index. We can do a couple of things. The logic to produce the columns table information could be made tolerant of not having a datatype reference (currently it just skips the record, which was the old behavior and limited to a corner case with mapping class columns). We can pass in the built in type information during the load of the model based indexes so that the datatype uuid references get properly resolved. If Designer does not want to keep reindexing the built-in datatypes, that would be fine - but it still needs to index new enterprise types. > Importing tables from a deployed VDB does not import columns > ------------------------------------------------------------ > > Key: TEIID-1149 > URL: https://jira.jboss.org/browse/TEIID-1149 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.0 > Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final > Reporter: Paul Nittel > Attachments: NoColumns.png, TeiidDes-506Projects.zip > > > I created, and deployed, a VDB containing source and view models. I am able to query these tables. > I created a new project and into that project I attempted to import a view model's table from the previously-created VDB. What I found in the imported was the models and tables were shown, but no columns were available for import. Once imported, the tables did have no columns. > Screenshot and other stuff attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1149) Importing tables from a deployed VDB does not import columns

by John Verhaeg (JIRA)

[ https://jira.jboss.org/browse/TEIID-1149?page=com.atlassian.jira.plugin.s... ] John Verhaeg moved TEIIDDES-506 to TEIID-1149: ---------------------------------------------- Project: Teiid (was: Teiid Designer) Key: TEIID-1149 (was: TEIIDDES-506) Affects Version/s: 7.0 (was: 7.0) Component/s: JDBC Driver (was: Import/Export) > Importing tables from a deployed VDB does not import columns > ------------------------------------------------------------ > > Key: TEIID-1149 > URL: https://jira.jboss.org/browse/TEIID-1149 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.0 > Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final > Reporter: Paul Nittel > Attachments: NoColumns.png, TeiidDes-506Projects.zip > > > I created, and deployed, a VDB containing source and view models. I am able to query these tables. > I created a new project and into that project I attempted to import a view model's table from the previously-created VDB. What I found in the imported was the models and tables were shown, but no columns were available for import. Once imported, the tables did have no columns. > Screenshot and other stuff attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-986) Add the ability to monitor other MM logs

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-986?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-986: -------------------------------- Fix Version/s: (was: 7.1) > Add the ability to monitor other MM logs > ----------------------------------------- > > Key: TEIID-986 > URL: https://jira.jboss.org/browse/TEIID-986 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Reporter: Van Halbert > Assignee: Ted Jones > > Add the ability to monitor other MM Logs. (i.e., HC log, ODBC, JGroups, Auditing) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2010