September 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-696) Add unit test coverage for use of a procedure variable as non join criteria

by Larry O'Leary (JIRA)

Add unit test coverage for use of a procedure variable as non join criteria --------------------------------------------------------------------------- Key: TEIID-696 URL: https://jira.jboss.org/jira/browse/TEIID-696 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 6.0.0, 6.1.0, 6.2.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Priority: Minor Fix For: 6.2.0 Add regression test coverage to verify the following query scenario doesn't result in the referenced procedure variable being pushed to the connector: SELECT pm1.g1.e1 AS pm1g1e1, pm1.g2.e1 AS pm1g2e1, pm1.g1.e2 AS pm1g1e2, pm1.g2.e2 AS pm1g2e2 FROM pm1.g1 LEFT OUTER JOIN pm1.g2 ON pm1.g1.e1 = pm1.g2.e1 AND pm1.g2.e2 = VARIABLES.myVar -- 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

16 years, 6 months

2
3
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 Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-225?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-225: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Targeting test issues to 6.3 > 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/jira/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 > Assignee: Greg Haber > Priority: Minor > Fix For: 6.3.0 > > > 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-408) logging controls/maintenance capabilities for transaction logging

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-408?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-408. ---------------------------------- Fix Version/s: 6.2.0 (was: 6.3.0) Resolution: Done Built-in database logging was removed in 6.2, rather administrators can use log4j appenders to control database logging. If database logging is brought back as a full-feature, then we'll reconsider having built-in maintenance. > logging controls/maintenance capabilities for transaction logging > ----------------------------------------------------------------- > > Key: TEIID-408 > URL: https://jira.jboss.org/jira/browse/TEIID-408 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 7.x > Reporter: Marc Shirley > Fix For: 6.2.0 > > > case 6664 > some type of control or maintenance capabilities should be added to Console to control the logging of transactions, metamatrix commands, and data source commands. This could even be the ability to disable database logging specifically for these commands. Currently, if these are turned on, the database can be filled up with these messages, and will have to be manually purged or maintained. The case that triggered this request had the following sizes of log tables: > TX_SRCCMDLOG - 37MB > TX_SQL_PK - 59MB > TX_SQL - 367MB > TX_MMXCMDLOG - 448MB -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Reopened: (TEIID-408) logging controls/maintenance capabilities for transaction logging

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-408?page=com.atlassian.jira.plug... ] Steven Hawkins reopened TEIID-408: ---------------------------------- Changing status from done > logging controls/maintenance capabilities for transaction logging > ----------------------------------------------------------------- > > Key: TEIID-408 > URL: https://jira.jboss.org/jira/browse/TEIID-408 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 7.x > Reporter: Marc Shirley > Fix For: 6.2.0 > > > case 6664 > some type of control or maintenance capabilities should be added to Console to control the logging of transactions, metamatrix commands, and data source commands. This could even be the ability to disable database logging specifically for these commands. Currently, if these are turned on, the database can be filled up with these messages, and will have to be manually purged or maintained. The case that triggered this request had the following sizes of log tables: > TX_SRCCMDLOG - 37MB > TX_SQL_PK - 59MB > TX_SQL - 367MB > TX_MMXCMDLOG - 448MB -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-408) logging controls/maintenance capabilities for transaction logging

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-408?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-408. ---------------------------------- Resolution: Out of Date > logging controls/maintenance capabilities for transaction logging > ----------------------------------------------------------------- > > Key: TEIID-408 > URL: https://jira.jboss.org/jira/browse/TEIID-408 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 7.x > Reporter: Marc Shirley > Fix For: 6.2.0 > > > case 6664 > some type of control or maintenance capabilities should be added to Console to control the logging of transactions, metamatrix commands, and data source commands. This could even be the ability to disable database logging specifically for these commands. Currently, if these are turned on, the database can be filled up with these messages, and will have to be manually purged or maintained. The case that triggered this request had the following sizes of log tables: > TX_SRCCMDLOG - 37MB > TX_SQL_PK - 59MB > TX_SQL - 367MB > TX_MMXCMDLOG - 448MB -- 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

16 years, 6 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-367?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-367. -------------------------------- > 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.3.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

16 years, 6 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-368?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-368. -------------------------------- > 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: 7.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

16 years, 6 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-371?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-371. -------------------------------- > 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.3.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

16 years, 6 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-369?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-369. -------------------------------- > 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: 7.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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-441) Expand the requires restart property

by Steven Hawkins (JIRA)

Expand the requires restart property ------------------------------------ Key: TEIID-441 URL: https://jira.jboss.org/jira/browse/TEIID-441 Project: Teiid Issue Type: Sub-task Components: Common, Console Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 Requires restart instead of a simple boolean should be an enum = {none, service, process, cluster}, any configuration property would default to process restart. any service property would default to service restart. -- 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

16 years, 6 months

2
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2009