July 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (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 resolved TEIID-986. --------------------------------- Resolution: Out of Date All Teiid server logging is through log4j. > 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-951) Add/Verify ipv6 readiness

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-951?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-951: -------------------------------- Fix Version/s: 7.2 (was: 7.1) Pushing to 7.2 > Add/Verify ipv6 readiness > ------------------------- > > Key: TEIID-951 > URL: https://jira.jboss.org/browse/TEIID-951 > Project: Teiid > Issue Type: Feature Request > Components: Documentation, Query Engine > Affects Versions: 6.2.0 > Reporter: Marc Shirley > Fix For: 7.2 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Received request for ipv6 support to comply with Federal Government transition. -- 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

13 years, 11 months

1
0
0 / 0

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

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-250?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-250. --------------------------------- Resolution: Out of Date Marking as out of date. We will re-assess performance issues with CXF. > 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-987) Problem regarding how often availability is called on the Facet

by Ted Jones (JIRA)

[ https://jira.jboss.org/browse/TEIID-987?page=com.atlassian.jira.plugin.sy... ] Ted Jones updated TEIID-987: ---------------------------- Fix Version/s: 7.2 (was: 7.1) > Problem regarding how often availability is called on the Facet > --------------------------------------------------------------- > > Key: TEIID-987 > URL: https://jira.jboss.org/browse/TEIID-987 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.0 > Reporter: Van Halbert > Assignee: Ted Jones > Fix For: 7.2 > > > There's a problem where the Facet (resource) availability is being checked about 5 times consecutively for every resource. There is an embedded jopr issue regarding this issue (EMBJOPR-129) > However, until this can be fixed, we might have to add a system property to handle how often to allow availability to be checked to limit the calls. Otherwise, this could a large processing overhead. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-217) LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result

by Larry O'Leary (JIRA)

[ https://jira.jboss.org/browse/TEIID-217?page=com.atlassian.jira.plugin.sy... ] Larry O'Leary updated TEIID-217: -------------------------------- > LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-217 > URL: https://jira.jboss.org/browse/TEIID-217 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: Michael Walker > Priority: Minor > Fix For: 7.2 > > > If an attribute appears more than once, we should have some way to return all values. Currently, we only return one value, with no rhyme, reason, or determinism as to which one gets returned. Implementing this is difficult when multiple attributes appear more than once, of course. But a simple example of where this problem rears it's head is in modeling LDAP groups. Groups typically have repeating attributes to represent each member, and it would be nice to query all members of a given group, but impossible to do so with the current logic. > A sophisticated solution would create a normalized view of a DN, breaking out multi-valued attributes into a separate table that could be joined by a primary key. A simple solution might allow attributes to be flagged as "multi-valued", in which case, they could be maintained in a single denormalized table that represents all values in the DN. > If we build an importer for LDAP, we should consider how to best handle this issue in the importer design. -- 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

13 years, 12 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 Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-219?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-219: -------------------------------- Fix Version/s: 7.2 (was: 7.1) > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://jira.jboss.org/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 7.2 > > > 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-225) LDAP Connector should use base DN for table as base DN for updates as well as queries

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-225?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-225: -------------------------------- Fix Version/s: 7.2 (was: 7.1) > LDAP Connector should use base DN for table as base DN for updates as well as queries > ------------------------------------------------------------------------------------- > > Key: TEIID-225 > URL: https://jira.jboss.org/browse/TEIID-225 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Environment: MetaMatrix 5.5.3RC2 > Reporter: Greg Haber > Priority: Minor > Fix For: 7.2 > > > Ramesh had a great idea earlier today on the LDAP connector: > [Ramesh] Why not search base info along with PK information to build the unique > DN? That seems possible right? > [Greg] Yes, that is a great idea! I will put in a JIRA for that (small code change, changing name of "search base" to just "base", and doc change). Probably we should have both relative and fully qualified DNs accepted here. Note however that the base may be several levels higher up in the tree then where you want to put the entry, so the base DN may be "ou=people,dc=company,dc=com", with a relative DN of "uid=ghaber,ou=newyork" here. -- 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

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-239) ENHANCEMENT: Costing beyond cardinality sould be propogated

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-239?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-239: -------------------------------- Fix Version/s: 7.2 (was: 7.1) > ENHANCEMENT: Costing beyond cardinality sould be propogated > ----------------------------------------------------------- > > Key: TEIID-239 > URL: https://jira.jboss.org/browse/TEIID-239 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.2 > > > Defect Tracker #24037: Currently values for ndv and nnv are recalculated at each plan node based upon the value at the physical layer. This is not a good estimate. Instead, these values should be propagated through the plan just like the cardinality and adjusted appropriately for join, unions, etc. It may also be good to allow the use of costing metadata on virtual layers. -- 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

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-885) CTC vdbs should use appropriate capabilities

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-885?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-885: -------------------------------- Fix Version/s: 7.2 (was: 7.1) > CTC vdbs should use appropriate capabilities > -------------------------------------------- > > Key: TEIID-885 > URL: https://jira.jboss.org/browse/TEIID-885 > Project: Teiid > Issue Type: Quality Risk > Components: Integration Tests > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Warren Gibson > Fix For: 7.2 > > > The CTC test vdbs currently use SimpleCapabilities rather than the actual source capabilities. This means that very little push down support is ever tested by CTC. -- 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

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1090) Request to add a Google Apps/Calendar Connector

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1090?page=com.atlassian.jira.plugin.s... ] Steve Hawkins updated TEIID-1090: --------------------------------- Fix Version/s: 7.2 (was: 7.1) > Request to add a Google Apps/Calendar Connector > ------------------------------------------------ > > Key: TEIID-1090 > URL: https://jira.jboss.org/browse/TEIID-1090 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > Fix For: 7.2 > > > Customer is requesting that we add a MetaMatrix Google Apps/Calendar Connector to a future release. -- 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

13 years, 12 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