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: ---------------------------------- I'm actually not particularly interested in end user caching - I was just referring back to the example in Ramesh's comment on Feb 19. Let me clarify the use case that I'm really interested in (or, more accurately, that a current customer of the MetaMatrix product is interested in solving down the road with Teiid): -Most of the read requests at this customer are for a relatively small (several GB) set of reference data, with the data source guaranteed not to change during the business day (all updated happen during a small, well-defined overnight period). -Many different end users at the customer access this reference data. -The current data source systems are overworked so they want to avoid sending more requests back to these sources. -They are not interested in setting up additional replication of the data into more relational databases - that has been their current approach to incrementally add more capacity, but every additional replication increases complexity of data distribution, and they end up with the relational database as a bottleneck. So this is a case where server side intermediate result set caching with heavy use of in-memory caching mechanisms is a great fit. They can warm the cache at the beginning of each day by issuing a set of queries for the data to be cached, and set cache expiration so that the results will be stored by cache for the duration of the business day. And this is certainly doable without a distributed cache - they would just need to warm each JVM individually, instead of doing it on the Teeid cluster as a whole and relying on the distributed cache mechanism to get results to each JVM. But that adds some complexity to the management of the caching jobs (especially as they grow to have potentially several dozen JVMs in their installation) - so long term, distributed cache functionality would be very useful. In other words, it isn't the performance of the cache population that is the question, it is the management of the population activity with a large number of JVMs. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-366) SFDC importer plugin has copies of lots of 3rd party jars that maybe should be in sep plugins

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-366?page=com.atlassian.jira.plug... ] Van Halbert reassigned TEIID-366: --------------------------------- Assignee: (was: Van Halbert) > SFDC importer plugin has copies of lots of 3rd party jars that maybe should be in sep plugins > --------------------------------------------------------------------------------------------- > > Key: TEIID-366 > URL: https://jira.jboss.org/jira/browse/TEIID-366 > Project: Teiid > Issue Type: Quality Risk > Components: Common, Documentation, Misc. Connectors > Affects Versions: 6.0.0 > Environment: Designer 5.5.3 MS1 build > Reporter: Greg Haber > Priority: Minor > Fix For: 6.1.0 > > > I noticed that as of MS1, the SFDC importer plugin contains a lot of copies of third party jars, most Apache Axis/Apache Commons stuff. In many cases, these same jars are also in the com.metamatrix.modeler.dqp_5.5.3 plugin since they are also needed by the SFDC connector. I also noticed that some of our other Designer plugins that use external jars put those jars in their own plugins, and import the plugin, rather than putting them in the same plugin as our own code. > We should consider pulling these jars out of the SFDC importer plugin and putting them in their own plugins (which the SFDC importer plugin can then import), or simply importing them in the SFDC importer plugin from the DQP plugin. > The same problem exists to a much lesser degree in the WSDL importer (just the commons-codec-1.2.jar is duplicated in that one). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-309) System Host setup issues

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-309?page=com.atlassian.jira.plug... ] Van Halbert resolved TEIID-309. ------------------------------- Resolution: Done These issues have been completed > System Host setup issues > ------------------------ > > Key: TEIID-309 > URL: https://jira.jboss.org/jira/browse/TEIID-309 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Fix For: 6.1.0 > > > 1) izpack does not make the startserver, stopserver, scripts as executable in the linux > 2) There is no option for *not* starting the server (either way it does not look like starting the server). This option should be extended to "setupmm" driven process too, with additional property. > 3) multicast port is not available in the IZpack + it is hard coded; Any two machines are seeing each other on the same multicast address. This needs to be fixed as soon as possible.(FEDERATE-340) > 4) System name is always defaulting to $hostname, even when it is blank. I fixed this in install. > 5) With "systenhostsetup.sh" I can not pass in the properties file, it is looking for the file in a fixed location. > 6) systemhostsetup.sh creates the "metamatrix.properties" file, but does not write to the configuration about what it's config name is, thus never can be started. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-371) System state should reflect the state and allow start/stop/restart of Membership Domains

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-371?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-371: ------------------------------- Component/s: Console Server Fix Version/s: 6.1.0 > System state should reflect the state and allow start/stop/restart of Membership Domains > ---------------------------------------------------------------------------------------- > > Key: TEIID-371 > URL: https://jira.jboss.org/jira/browse/TEIID-371 > Project: Teiid > Issue Type: Feature Request > Components: Console, Server > Affects Versions: 6.0.0 > Environment: MMServer 5.5.3 EA5 > MMConsole 5.5.3 EA5 > Server: RHEL5 Kernel 2.6.18-53.1.14.el5 > Console: Fedora 8 Kernel 2.6.26.3-14.fc8 > Reporter: Larry O'Leary > Priority: Minor > Fix For: 6.1.0 > > > When modifying properties for a membership domain a dialog appears and tells you that changes will not take affect until the provider is restarted in the System State Panel. This does not appear possible and the only method is to bounce the system. > Also, in cases where a membership domain provider fails to start due to property errors or conflicts, there is no indication of this in the Console. > The System State panel should be updated to show status and allow restart of membership domain providers. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-368) System state should give state details

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-368?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-368: ------------------------------- Component/s: Console Server Fix Version/s: 6.x > System state should give state details > -------------------------------------- > > Key: TEIID-368 > URL: https://jira.jboss.org/jira/browse/TEIID-368 > Project: Teiid > Issue Type: Feature Request > Components: Console, Server > Affects Versions: 6.0.0 > Environment: N/A > Reporter: Larry O'Leary > Priority: Minor > Fix For: 6.x > > > The system state displayed in the Console (or via the Admin API) should allow for displaying individual state details. For example, if I have a connector with the state of "Failed Initialization" I should be able to see information about the reason and cause of that sate including state change information: > State: Failed Initialization > State changed at 1:52 PM CDT by loleary > Details: [MetaMatrix][Oracle JDBC Driver]Error establishing socket. Unknown host: <host> > or > State: Running > State changed at 1:53 PM CDT by loleary > Details: Service started > or > State: Stopped > State changed at 1:54 PM CDT by MetaMatrixAdmin > Details: Service stopped > or > State: Data Source Unavailable > State changed at 1:59 PM CDT by DataSourceMonitor > Details: [MetaMatrix][Oracle JDBC Driver]Connection refused > Basically this would require all service state changes to be accompanied by a meaningful state message. In the case of an exception or warning base cause of the exception should be indicated as a message (no stack traces as that is what the logs are for). For successful state changes this would be just an indication message to show a generic state detail like "Started", "Stopped", "Restarted", etc. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-367) Add a validation step to security provider definition.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-367?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-367: ------------------------------- Component/s: Console Server Fix Version/s: 6.1.0 Does updating with Admin API provides any kind of indication that this is successful? > Add a validation step to security provider definition. > ------------------------------------------------------ > > Key: TEIID-367 > URL: https://jira.jboss.org/jira/browse/TEIID-367 > Project: Teiid > Issue Type: Feature Request > Components: Console, Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > It would be good for the MembershipDomain provider wizard to offer an optional validation step where an instance of the membership domain is created, initialized, and asked for the groups. Any errors would be shown in the wizard. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-372) Queries of expired sessions persist "too long"

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-372?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-372: ------------------------------- Component/s: Server Fix Version/s: 6.x I would advise to retest this with new version, see if the problem still exists otherwise we close this. > Queries of expired sessions persist "too long" > ---------------------------------------------- > > Key: TEIID-372 > URL: https://jira.jboss.org/jira/browse/TEIID-372 > Project: Teiid > Issue Type: Task > Components: Server > Affects Versions: 6.0.0 > Environment: All > Reporter: Paul Nittel > Fix For: 6.x > > > The Server Connection Test includes a test where a JDBC session is created in jdbcisql, and then jdbcisql is killed (CTRL-C). After 30 - 50 minutes, that session is expired by the system and it is removed from the Sessions panel in the Console. > I noticed some time later that a query, belonging to the now gone session, was still showing up in the Queries panel. Several others are also hanging around. One was submitted over 2 hours earlier. > Refreshing the Console's panels does not help. Stopping and starting the Console doesn't help, either. > The queries should be removed from the system at (roughly) the same time the session is expired, or terminates on its own. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-362) Console - Create New Data Roles panel step 2 & 3 displays wrong VDB version #

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-362?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-362: ------------------------------- Component/s: Console Fix Version/s: 6.1.0 > Console - Create New Data Roles panel step 2 & 3 displays wrong VDB version # > ----------------------------------------------------------------------------- > > Key: TEIID-362 > URL: https://jira.jboss.org/jira/browse/TEIID-362 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: MM Console in Windows environment on slntmm06 > Reporter: Warren Gibson > Priority: Minor > Fix For: 6.1.0 > > > Creating New Data Roles: > Step 1 panel I selected the VDB and version 2 > Steps 2 & 3 panels show VDB version 1 > Step 4 shows VDB version 2 > Data Roles were actually created for VDB version 2 but steps 2 & 3 were displaying the wrong version # -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-369) Connector properties page should have a "Test" button to test connector

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-369?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-369: ------------------------------- Component/s: Console Fix Version/s: 6.x > Connector properties page should have a "Test" button to test connector > ----------------------------------------------------------------------- > > Key: TEIID-369 > URL: https://jira.jboss.org/jira/browse/TEIID-369 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Environment: NA > Reporter: Larry O'Leary > Priority: Minor > Fix For: 6.x > > > The Connector properties/configuration page should have a button/option to test the connector. This will allow the user to verify the connector prior to deploying it to the server. On an existing connector it allows them to test the connector prior to applying the changes. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-365) Console Error Message when logging into MM Server is confusing

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-365?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-365: ------------------------------- Component/s: Console Fix Version/s: 6.1.0 This is bizarre, the screen shows three different connection properties; 05 connected, 07 trying to connect, 06 error. > Console Error Message when logging into MM Server is confusing > -------------------------------------------------------------- > > Key: TEIID-365 > URL: https://jira.jboss.org/jira/browse/TEIID-365 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Logging into MetaMatrix Server slntmm07 with MetaMatrix Console > Reporter: Warren Gibson > Priority: Minor > Fix For: 6.1.0 > > Attachments: slntmm07logon.jpg > > > When attempting to log into slntmm07 I am presented with a dialog box stating "Connection to mm://slntmm06:50201 for user metamatrixadmin already exists." > While it is true I am logged into slntmm06, that has nothing to do with me logging into slntmm07 and the dialog is confusing. See attached file slntmm07logon.jpg -- 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, 2 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