March 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-409) server port number should be checked for availability when creating a second mmprocess

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-409?page=com.atlassian.jira.plug... ] Ramesh Reddy moved JBEDSP-242 to TEIID-409: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-409 (was: JBEDSP-242) Component/s: Server (was: Documentation) (was: Server) Fix Version/s: 6.1.0 (was: Westport) Affects Version/s: 6.x (was: 5.5) (was: 5.5.1) (was: 5.5.2) > server port number should be checked for availability when creating a second mmprocess > -------------------------------------------------------------------------------------- > > Key: TEIID-409 > URL: https://jira.jboss.org/jira/browse/TEIID-409 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.x > Reporter: Marc Shirley > Fix For: 6.1.0 > > > Creating a second process on a server increments the port number by one from the primary process. This port number does not seem to be checked for availability, and so, if the second process's port is already in use, then status of the second process will be unreliable (it flickers between "Running" and "Not Started" states). One or more of the below actions should be taken: > 1) A check should be added to the process of adding a second process to detect whether a port is already in use. > 2) A KI entry should be made to cover the issue. > 3) Steps should be added to the Console User's Guide and/or Server Tuning Guide to advise the reader to make sure the port assigned to the second process is not in use by another application. -- 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, 9 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-408?page=com.atlassian.jira.plug... ] Ramesh Reddy moved JBEDSP-160 to TEIID-408: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-408 (was: JBEDSP-160) Component/s: Server (was: Server) Fix Version/s: 6.2.0 (was: Westport) Affects Version/s: 6.x (was: Westport) > 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: 6.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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-407) Update sessionservice properties

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-407?page=com.atlassian.jira.plug... ] Ramesh Reddy moved JBEDSP-830 to TEIID-407: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-407 (was: JBEDSP-830) Component/s: Server (was: Server) Fix Version/s: 6.1.0 (was: Westport) Affects Version/s: 6.x (was: Westport) > Update sessionservice properties > -------------------------------- > > Key: TEIID-407 > URL: https://jira.jboss.org/jira/browse/TEIID-407 > Project: Teiid > Issue Type: Task > Components: Server > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The session service was simplified, we need to remove properties that are no longer in use. Only the following are still in use: > security.session.terminationHandlers > metamatrix.session.max.connections > metamatrix.session.time.limit > metamatrix.session.sessionMonitor.ActivityInterval -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-406) Extra commands for union are collected when the falg is set to embedded

by Li Liang (JIRA)

Extra commands for union are collected when the falg is set to embedded ------------------------------------------------------------------------ Key: TEIID-406 URL: https://jira.jboss.org/jira/browse/TEIID-406 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Li Liang Assignee: Li Liang Fix For: 6.0.0 This is from a customer case (269005). CommandCollectorVisitor collects extra commands for the union when the flag is set to embedded only. -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Moved: (TEIID-405) Allow importing a VDB file from a URL (not just the local file system)

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-405?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-796 to TEIID-405: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-405 (was: JBEDSP-796) Component/s: Console (was: Console) Fix Version/s: 6.0.0 (was: Westport) Affects Version/s: 6.1.0 (was: 5.5.3) > Allow importing a VDB file from a URL (not just the local file system) > ---------------------------------------------------------------------- > > Key: TEIID-405 > URL: https://jira.jboss.org/jira/browse/TEIID-405 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.1.0 > Reporter: Randall Hauch > Priority: Minor > Fix For: 6.0.0 > > > The Console currently has the ability to import a VDB file from the local file system. A great enhancement to this would be the ability to import a VDB from a URL, allowing an administrator to import a VDB file that is located anywhere accessible via a URL (e.g., SVN, DNA, WebDAV, etc.), without requiring the administrator to fetch the file locally first. Of course, fetching it locally is still a valid (and not difficult) workaround. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-404) 1-way and 2-way SSL to MMx must support different keystore file names within a cluster

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-404?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-900 to TEIID-404: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-404 (was: JBEDSP-900) Component/s: Server (was: Server) Fix Version/s: 6.0.0 (was: Westport) Affects Version/s: 6.1.0 (was: 5.5) > 1-way and 2-way SSL to MMx must support different keystore file names within a cluster > -------------------------------------------------------------------------------------- > > Key: TEIID-404 > URL: https://jira.jboss.org/jira/browse/TEIID-404 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.1.0 > Reporter: Larry O'Leary > Fix For: 6.0.0 > > > Defect Tracker #24283: File naming conventions require a keystore file to be prefixed with the machine's host name. This creates a problem when deploying certificates for use with SSL to a MetaMatrix System as the keystore on each MetaMatrix Server has a different name. Currently, the MMConsole only allows you to set a key store file name that will be used system wide. > We will need the ability to define a key store file name on a per host and possibly a per VM basis. This could be accomplished in many different manners. > The recommended implementation would be to simply move the SSL Resource configuration to the process and host level. This would allow an administrator to continue to use the Console to configure SSL. > At the host level, the administrator could set the default key store file name to be used for all VM(s) deployed to that host. At the VM level, the administrator could set a key store file name value that will override the default host level key store file name property. > This should also be done for the client trust store property to support 2-way SSL. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-403) ESB transport capabilitiy for connector framework

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-403?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-174 to TEIID-403: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-403 (was: JBEDSP-174) Component/s: Misc. Connectors (was: Connectors) Fix Version/s: 6.x (was: Westport) > ESB transport capabilitiy for connector framework > ------------------------------------------------- > > Key: TEIID-403 > URL: https://jira.jboss.org/jira/browse/TEIID-403 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Marc Shirley > Assignee: Jerry Helbling > Fix For: 6.x > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-143) Query should 'find' connector types and jars rather than have them predefined in the config.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-143: ------------------------------- Fix Version/s: 6.2.0 (was: 6.1.0) > Query should 'find' connector types and jars rather than have them predefined in the config. > -------------------------------------------------------------------------------------------- > > Key: TEIID-143 > URL: https://jira.jboss.org/jira/browse/TEIID-143 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: John Doyle > Fix For: 6.2.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Currently, dqp as delived with Designer is preconfigured with connector types. I think it should discover the connectors that are available upon startup. This would make it easier to add connectors to a kit. The current process for adding a connector to a kit is manual and error prone. We have problems with it on nearly every release. > This is also an attractive feature for embedding query in other environments. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-399) Oracle Spatial SQL translator drops the LIMIT clause.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-399?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-399. -------------------------------- Resolution: Done changed OracleSpatialSQLTranslator to inherit OracleSQLTranslator > Oracle Spatial SQL translator drops the LIMIT clause. > ----------------------------------------------------- > > Key: TEIID-399 > URL: https://jira.jboss.org/jira/browse/TEIID-399 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: John Doyle > > The LIMIT SQL clause is not having an effect on our SQL queries. In our case, we are using the Oracle Spatial connector which interfaces with an Oracle 10g database. What configuration or connector changes are needed so we can leverage the LIMIT clause for controlling the fetch size of our result sets which are derived from Oracle? > I am running the following query: > SELECT SEQ_NUM > FROM IBSBINO_Physical.IBSBINO > LIMIT 5 > I expect to get back 5 rows of data, but get back the entire table > instead. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-156) Console should allow for setting arbitrary propeties

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-156?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-156: ------------------------------- Fix Version/s: 6.2.0 (was: 6.1.0) Affects Version/s: 6.1.0 (was: 6.2.0) > Console should allow for setting arbitrary propeties > ---------------------------------------------------- > > Key: TEIID-156 > URL: https://jira.jboss.org/jira/browse/TEIID-156 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.1.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > It would be especially useful for custom connectors, or even our own connectors with mid release enhancements, to allow the console to set arbitrary properties rather than requiring hand modification of the config. -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2009