October 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1187) Refine vdb version logic

by Steve Hawkins (JIRA)

Refine vdb version logic ------------------------ Key: TEIID-1187 URL: https://jira.jboss.org/browse/TEIID-1187 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 We no longer have a built in configuration repository and we rely on container scans to do deploys, so we have lost the ability to internally control the notion of a deployed vdb version. We should strive for the following: 1. Overwrite of a deployed vdb should not invalidate or otherwise corrupt current connections. 2. Switching to a different vdb as the new default for a particular name should not require two deployments of the same vdb. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1055) Secure profile service access

by Ramesh Reddy (JIRA)

Secure profile service access ----------------------------- Key: TEIID-1055 URL: https://jira.jboss.org/jira/browse/TEIID-1055 Project: Teiid Issue Type: Task Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Fix For: 7.0 As of 7.0 M3 release, the "Profile Service" access is not secure. Currently the JOPR plug-in and Teiid Admin API, force users to authenticate with "jmx-console" security domain, both these do not prevent the direct access to the "Profile Service" EJB directly. Profile Service can be deployed as secure EJB, such that it would require a login context to be authenticated before user has access to this bean. This needs to be configured and tested. Also document, how to configure the profile service as secure service. Also, AdminFactory class, which provides Admin connections, need to work with secure "Profile Service". -- 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

13 years, 8 months

5
8
0 / 0

[JBoss JIRA] Created: (TEIID-1213) Procedure results should be cachable as well

by Steve Hawkins (JIRA)

Procedure results should be cachable as well -------------------------------------------- Key: TEIID-1213 URL: https://jira.jboss.org/browse/TEIID-1213 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1.1 Virtual procedure invocations should be cached in a mechanism similar to materialized views. This is to fully replace the MetaMatrix functionality of source query caching. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1221) Query Processing Uncorrelated subquery evaluation - Not saving state causing re-execution without closing prior connection

by Warren Gibson (JIRA)

Query Processing Uncorrelated subquery evaluation - Not saving state causing re-execution without closing prior connection -------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1221 URL: https://jira.jboss.org/browse/TEIID-1221 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Environment: Teiid 7.1 Final; PostgreSQL83 DB Reporter: Warren Gibson Assignee: Steve Hawkins Query Testing - The following query is causing an issue which stops further processing. SELECT stringkey, (SELECT intkey from BQT1.SmallA as b where Intnum = 22) FROM BQT1.SmallA order by stringkey. Steve H stated this is related to uncorrelated subquery evaluation - Not saving state from one execution to the next which is causing a re-execute without closing the prior connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-1211) Refine load-balancing support in AS

by Steve Hawkins (JIRA)

Refine load-balancing support in AS ----------------------------------- Key: TEIID-1211 URL: https://jira.jboss.org/browse/TEIID-1211 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1.1 In an AS connection pool, an XAConnection does not receive a notification of a connection.close, so our post-connection load-balancing logic will never kick in. For environments with a low/infrequent number of client connections, this will produce a poor load distribution. Possible Solutions: 1. Ensure proper tracking of the transation state and switch servers after a commit/rollback. This however would also require that session level temporary tables are replicated (although that replication logic should be added as part of the materialization feature). And would cause potential cache misses or other minor issues with session level deterministic functions. 2. Promote the use of Teiid directly through our own DataSource and handle transaction enlist/delist logic appropriately. Users would instead use a jboss beans.xml file to create a named instance of the datasource in JNDI. The appeal of this solution is that it we are architected to not require the use of a pool (settings for max connections, statement pooling, are mostly irrelevant for local connections to Teiid). We have our own thread pooling, etc. 3. See if we can get some AS patch to also pass connection events to PooledConnections. Another thing that may need addressed is runtime discovery of additional hosts, if not we could also add an option to pick up hosts and connection information from an external file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1142) Teiid should work with EAP 5.1

by Ramesh Reddy (JIRA)

Teiid should work with EAP 5.1 ------------------------------- Key: TEIID-1142 URL: https://jira.jboss.org/browse/TEIID-1142 Project: Teiid Issue Type: Task Components: Build/Kits Affects Versions: 7.0 Reporter: Ramesh Reddy Priority: Critical Fix For: 7.1 Teiid kits must be able deploy inside the JBoss EAP 5.1 and work correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIID-1188) Error while reading the template properties for LDAP

by Ramesh Reddy (JIRA)

Error while reading the template properties for LDAP ---------------------------------------------------- Key: TEIID-1188 URL: https://jira.jboss.org/browse/TEIID-1188 Project: Teiid Issue Type: Bug Components: LDAP Connector Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 7.1 groovy:000> getTemplatePropertyDefinitions("connector-ldap"); ERROR org.teiid.adminapi.AdminComponentException: Failed to find template for: translator-connector-ldap at org.teiid.client.util.ExceptionUtil.convertException (ExceptionUtil.java:72) at org.teiid.net.socket.SocketServerConnection$ServerConnectionInvocationHandler.invoke (SocketServerConnection.java:239) at $Proxy7.getTemplatePropertyDefinitions (Unknown Source -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1222) Partially qualified unambiguous virtual procedure problem resolving inputs.

by Steve Hawkins (JIRA)

Partially qualified unambiguous virtual procedure problem resolving inputs. --------------------------------------------------------------------------- Key: TEIID-1222 URL: https://jira.jboss.org/browse/TEIID-1222 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Priority: Minor Fix For: 7.1.1 Partially qualified unambiguous virtual procedures will not resolve inputs due to using the wrong qualified name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1204) Re-enable failover support

by Steve Hawkins (JIRA)

Re-enable failover support -------------------------- Key: TEIID-1204 URL: https://jira.jboss.org/browse/TEIID-1204 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 Failover support currently doesn't work due to sessions not being stored globally. It has been determined that we will not store sessions globally - since that presents a security risk and doesn't provide many benefits. So the failover support should feel free to re-authenticate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1223) Cache hint cannot be specified against set queries or callable statements

by Steve Hawkins (JIRA)

Cache hint cannot be specified against set queries or callable statements ------------------------------------------------------------------------- Key: TEIID-1223 URL: https://jira.jboss.org/browse/TEIID-1223 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Priority: Minor Fix For: 7.1.1 Due to looking for specific tokens in the parser we miss some cases where a cache hint is appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2010