February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-168) Remove resultset caching

by Greg Haber (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plug... ] Greg Haber commented on TEIID-168: ---------------------------------- Steve, will this caching implementation be distributed or will it be per-JVM? > 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

[JBoss JIRA] Created: (TEIID-348) Use generics in api

by Steven Hawkins (JIRA)

Use generics in api ------------------- Key: TEIID-348 URL: https://jira.jboss.org/jira/browse/TEIID-348 Project: Teiid Issue Type: Sub-task Components: Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 The new connector api should use generics where appropriate. -- 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
1
0 / 0

[JBoss JIRA] Created: (TEIID-351) Add proper support for GT and LT criteria

by Steven Hawkins (JIRA)

Add proper support for GT and LT criteria ----------------------------------------- Key: TEIID-351 URL: https://jira.jboss.org/jira/browse/TEIID-351 Project: Teiid Issue Type: Bug Components: LDAP Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.0.0 In cleaning up the connector api I noticed that proper LT and GT support needs to be added. -- 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
2
0 / 0

[JBoss JIRA] Updated: (TEIID-138) Convert Common XML Connector to Axis2

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-138?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-138: --------------------------------- Fix Version/s: 6.1.0 (was: 6.0.0) Complexity: Medium > Convert Common XML Connector to Axis2 > ------------------------------------- > > Key: TEIID-138 > URL: https://jira.jboss.org/jira/browse/TEIID-138 > Project: Teiid > Issue Type: Sub-task > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.1.0 > > -- 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-137) Remove the HTTPClient Usage from the XML Connector and use the Common XML Connector

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-137?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-137: --------------------------------- Fix Version/s: 6.1.0 (was: 6.0.0) Complexity: Medium > Remove the HTTPClient Usage from the XML Connector and use the Common XML Connector > ----------------------------------------------------------------------------------- > > Key: TEIID-137 > URL: https://jira.jboss.org/jira/browse/TEIID-137 > Project: Teiid > Issue Type: Sub-task > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.1.0 > > > Need to remove the HTTPClient usage from the XML Connector and use the Axis client in the Common XML Connector to reduce download size -- 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] Resolved: (TEIID-133) Refactor XML Connector to Common XML Connector to Minimize Dependencies

by Ted Jones (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-133?page=com.atlassian.jira.plug... ] Ted Jones resolved TEIID-133. ----------------------------- Resolution: Done Re-factored common dependencies in XML and SalesForce connectors to a new POM project: connector-xml-common. > Refactor XML Connector to Common XML Connector to Minimize Dependencies > ----------------------------------------------------------------------- > > Key: TEIID-133 > URL: https://jira.jboss.org/jira/browse/TEIID-133 > Project: Teiid > Issue Type: Quality Risk > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.0.0 > > > Need to refactor the Axis client calls from XML Connector and SalesForce connector into a shared project to reduce the number of depencies and consequently reduce the size of the kit -- 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-104) Connector development documentation out-of-date

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-104?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-104: --------------------------------- Parent: TEIID-164 Issue Type: Sub-task (was: Bug) > Connector development documentation out-of-date > ----------------------------------------------- > > Key: TEIID-104 > URL: https://jira.jboss.org/jira/browse/TEIID-104 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Documentation > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > The included diagrams and documentation are not up-to-date with the limit, intersect, and except features. Documentation needs to be added for GlobalCapabilitiesProvider as well. -- 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-315) Add JDBC Connector developers guide

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-315?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-315: --------------------------------- Parent: TEIID-164 Issue Type: Sub-task (was: Task) > Add JDBC Connector developers guide > ----------------------------------- > > Key: TEIID-315 > URL: https://jira.jboss.org/jira/browse/TEIID-315 > Project: Teiid > Issue Type: Sub-task > Components: Documentation > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > -- 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] Resolved: (TEIID-191) connector-api enhancements

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-191?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-191. ---------------------------------- Resolution: Done Modified the behavior of existing warnings - they are now only available on the Statement Also partial result warnings are no longer aggregated Added BasicExecution that handles warnings. Need to document ConnectorLogger, ConnectorEnvironment.addWork, and Execution.getWarnings > connector-api enhancements > -------------------------- > > Key: TEIID-191 > URL: https://jira.jboss.org/jira/browse/TEIID-191 > Project: Teiid > Issue Type: Feature Request > Components: Connector API > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Add the ability for connector jobs - ConnectorEnvironment.addWork(Runnable) and possibly repeating tasks > Add isEnabled methods for log levels on connector logger > Add the ability to return warnings (as ConnectorExceptions) from an execution and allow them to flow all the way to 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] Assigned: (TEIID-66) dqp lifecycle issues

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-66?page=com.atlassian.jira.plugi... ] Ramesh Reddy reassigned TEIID-66: --------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > dqp lifecycle issues > -------------------- > > Key: TEIID-66 > URL: https://jira.jboss.org/jira/browse/TEIID-66 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 6.0.0 > > > There are some exceptions (see below) happening during Embedded shutdown. The CacheProvider looks like it's assuming that it's a true singleton, but the EmbeddedGuiceModule is created and the Injector is set on the ResourceFinder with ever EmbeddedConnection created. That's causing us to attempt the mbean registration and cache creation with every connection, which seems very troubling with simultaneous connections. What do you think about the following: > 1. Why should we initiate an implicit shutdown with no connections? Why not implicitly start, but require an explicit shutdown. > 2. We should at least promote the set of the injector to the constructor of EmbeddedConnectionFactoryImpl (assuming 1 jboss cache per dqp), however I don't know enough about how we're using JBoss cache to know if that will work. It seems like we would need to use a cache region per dqp, not a separate cache. But if it is one cache per, then at the very least we would need to also change our mbean registration to have unique names. > 3. It looks like we can avoid the exception below if we first unregister the existing instance. Logically we'd like that to happen when JBossCacheFactory.destroy is called, so I'd be in favor of moving the mbean registration and dergistration logic into the JBossCacheFactory so that it has control over both sides. > > javax.management.InstanceAlreadyExistsException: jboss.cache:service=MetaMatrixCacheTree > > at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453) > > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484) > > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963) > > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) > > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) > > at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) > > at com.metamatrix.jdbc.CacheProvider.get(CacheProvider.java:51) > > at com.metamatrix.jdbc.CacheProvider.get(CacheProvider.java:40) > > at com.google.inject.BoundProviderFactory.get(BoundProviderFactory.java:60) > From Ramesh: > 3. Yes, this needs to be done. > 2. DQP only uses the cache for the resultset caching. I am kind of on > the fence about supporting multiple DQP instances, in a given VM. I do > not see that as serving much of the usecases. So, if we can relax that > requirement then we can always assume there is only one instance of the > DQP. Otherwise, depending upon how we use Cache we should be able to > segment cache by DQP instance identifier. > 1. Except for re-loading times, do you see any issue with this? Original > design wanted to see the Embedded as JDBC driver, such that when there > are no connections, it unloads itself and reduces the memory footprint > of the VM. It become more of who's responsibility is it to shutdown? If > we deployed this app server, or in pre-built tool like Squirrel. > Shutting down closes the connector bindings etc, that are active. -- 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