July 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-708) Connector metadata should be availble to the metadata connector

by Steven Hawkins (JIRA)

Connector metadata should be availble to the metadata connector --------------------------------------------------------------- Key: TEIID-708 URL: https://jira.jboss.org/jira/browse/TEIID-708 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.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

16 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIID-716) Connector Status can reported wrong or possibility of NPE

by Ramesh Reddy (JIRA)

Connector Status can reported wrong or possibility of NPE --------------------------------------------------------- Key: TEIID-716 URL: https://jira.jboss.org/jira/browse/TEIID-716 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 The connector status through ConnectorManager object currently represented through Boolean and rest of the states are derived from that. That seems limited, the connector state should be correctly propagated from ConnectorManager. In the cases of user context based connection pooling under Connector, where connections are made based on individual user credentials it is not possible to check if the connection is alive. In this situation current code has bug that can be result in the NPE. -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIID-484) Upgrade JGroups to 2.6.10

by Ramesh Reddy (JIRA)

Upgrade JGroups to 2.6.10 ------------------------- Key: TEIID-484 URL: https://jira.jboss.org/jira/browse/TEIID-484 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 Upgrade the JGroups version to 2.6.10 to be in sync with what is been used in AS 5.1.0. Need to make sure this is version is being used in EAP release before upgrade. -- 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
5
0 / 0

[JBoss JIRA] Created: (TEIID-656) URLHelper does not handle absolute windows file paths for the mmrofile protocol

by Steven Hawkins (JIRA)

URLHelper does not handle absolute windows file paths for the mmrofile protocol ------------------------------------------------------------------------------- Key: TEIID-656 URL: https://jira.jboss.org/jira/browse/TEIID-656 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.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

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-654) On MMResource, the connectionPool attribute is no longer valid because the feature to create connection pools and assign them to a resource is no longer offered

by Van Halbert (JIRA)

On MMResource, the connectionPool attribute is no longer valid because the feature to create connection pools and assign them to a resource is no longer offered ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-654 URL: https://jira.jboss.org/jira/browse/TEIID-654 Project: Teiid Issue Type: Bug Components: AdminApi, Server Affects Versions: 6.2.0 Reporter: Van Halbert Assignee: Van Halbert The feature to create connection pools and assign them to the resource has been removed. Therefore, the connectionPool attribute on the MMResource is no longer useful. -- 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] Created: (TEIID-686) Query engine should be able to plan and execute user queries based upon metadata from connectors

by Ramesh Reddy (JIRA)

Query engine should be able to plan and execute user queries based upon metadata from connectors ------------------------------------------------------------------------------------------------ Key: TEIID-686 URL: https://jira.jboss.org/jira/browse/TEIID-686 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Ramesh Reddy Assignee: Steven Hawkins Priority: Critical Fix For: 6.2.0 When the connectors supply the metadata natively rather than from VDB, query engine must able to query this metadata from connectors and able to use this information during resolving and planning of the user query. -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIID-485) Upgrade JBoss Cache to 3.1.0

by Ramesh Reddy (JIRA)

Upgrade JBoss Cache to 3.1.0 ---------------------------- Key: TEIID-485 URL: https://jira.jboss.org/jira/browse/TEIID-485 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 Upgrade JBoss Cache to 3.10 GA to be in sync with AS 5.1.0. Make sure this is the version used by the EAP 5.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

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-687) JDBC Connector should be Metadata Aware Connector

by Ramesh Reddy (JIRA)

JDBC Connector should be Metadata Aware Connector ------------------------------------------------- Key: TEIID-687 URL: https://jira.jboss.org/jira/browse/TEIID-687 Project: Teiid Issue Type: Sub-task Components: JDBC Connector Reporter: Ramesh Reddy Fix For: 6.2.0 Based on TEIID-685, JDBC Connector must implement this interface(s), so that any JDBC sources can be used in dynamic data integration -- 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
4
0 / 0

[JBoss JIRA] Created: (TEIID-695) Equality comparison of JoinPredicate returns true even when JoinPredicate criteria is different

by Larry O'Leary (JIRA)

Equality comparison of JoinPredicate returns true even when JoinPredicate criteria is different ----------------------------------------------------------------------------------------------- Key: TEIID-695 URL: https://jira.jboss.org/jira/browse/TEIID-695 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0, 6.1.0, 6.2.0 Reporter: Larry O'Leary Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 When comparing the following command objects the commands evaluate as equal when performing c1.equals(c2) even though the criteria is different in the two commands: c1 = SELECT bqt1.smalla.intkey, bqt1.smallb.intkey, bqt1.smalla.intnum, bqt1.smallb.intnum FROM bqt1.smalla LEFT OUTER JOIN bqt1.smallb ON bqt1.smalla.intkey = bqt1.smallb.intkey AND bqt1.smallb.intnum = 1 c2 = SELECT bqt1.smalla.intkey, bqt1.smallb.intkey, bqt1.smalla.intnum, bqt1.smallb.intnum FROM bqt1.smalla LEFT OUTER JOIN bqt1.smallb ON bqt1.smalla.intkey = bqt1.smallb.intkey This is due to the method com.metamatrix.query.sql.lang.JoinPredicate.equals(Object obj) referencing itself when getting the criteria from itself and the obj being passed in: ... List thisCrit = this.getJoinCriteria(); ... List otherCrit = this.getJoinCriteria(); ... -- 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
5
0 / 0

[JBoss JIRA] Created: (TEIID-701) Provide a single JDBC driver for "embedded" and "server" configurations

by Ramesh Reddy (JIRA)

Provide a single JDBC driver for "embedded" and "server" configurations ----------------------------------------------------------------------- Key: TEIID-701 URL: https://jira.jboss.org/jira/browse/TEIID-701 Project: Teiid Issue Type: Task Components: JDBC Driver Reporter: Ramesh Reddy Fix For: 6.2.0 Currently there are separate JDBC drivers for Embedded --> com.metamatrix.jdbc.EmbeddedDriver Server --> org.teiid.jdbc.TeiidDriver Combine the EmbeddedDriver functionality into TeiidDriver. Based on its URL format differentiate which runtime user wants to use. The URLs for runtimes are as follows Embedded ---> jdbc:metamatrix:<vdb-name>@<path-to>/deploy.properties;<additional-properties> Server ---> jdbc:teiid:<vdb-name>@mm://<host-name>:<port>;<additional-properties> 1) Deprecate EmbeddedDriver 2) Make embedded URL format to work with " jdbc:teiid:<vdb-name>@<path-to>/deploy.properties;<additional-properties>" (note s/mematrix/teiid/) 3) Make the TeiidDriver the only driver. Investigate if EmbeddedDataSource and TeiidDataSource can be combined, if true follow the same path. -- 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
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2009