August 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2177) Expand native-query support

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2177: ------------------------------------- Summary: Expand native-query support Key: TEIID-2177 URL: https://issues.jboss.org/browse/TEIID-2177 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 The native-query extension metadata is currently understood only by jdbc. We should add support in olap, ldap, salesforce, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
5
0 / 0

[JBoss JIRA] (TEIID-2176) Expose invoke procedures for querable sources

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2176: ------------------------------------- Summary: Expose invoke procedures for querable sources Key: TEIID-2176 URL: https://issues.jboss.org/browse/TEIID-2176 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 We should add procedures similar to invokeMDX that allow native query execution. This would compliment the canned native-query feature to allow fully dynamic query execution. TEIID-2111 will also provide vararg capabilities should we need it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] (TEIID-2122) Teiid Freezes while trying to get Connection

by Gautam Banerjee (JIRA)

Gautam Banerjee created TEIID-2122: -------------------------------------- Summary: Teiid Freezes while trying to get Connection Key: TEIID-2122 URL: https://issues.jboss.org/browse/TEIID-2122 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.7 Reporter: Gautam Banerjee Assignee: Steven Hawkins Hi, In Teiid 7.7.1 we are trying to get the connection from datasource. If the connection is made to a inactive vdb then processing freezes at getConnection(). If connection is made to a active vdb then processing continues. The relevant code is TeiidDataSource.getConnection(). Please resolve. Thanks Gautam -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

6
26
0 / 0

[JBoss JIRA] (TEIID-2095) Cannot use deployed WAR with HTTPBasic authentication

by Paul Nittel (JIRA)

Paul Nittel created TEIID-2095: ---------------------------------- Summary: Cannot use deployed WAR with HTTPBasic authentication Key: TEIID-2095 URL: https://issues.jboss.org/browse/TEIID-2095 Project: Teiid Issue Type: Bug Components: SOAP Services Affects Versions: 7.7.1 Environment: RHEL6 (SOA 5.3 ER5) Reporter: Paul Nittel Assignee: Steven Hawkins Fix For: 7.7.1 I created a WAR which specifies HTTPBasic security. My WAR definition specifies a role and the default realm (teiid-security). On the server, my datasource specifies PassthroughAuthentication=true. I have tried Security Deployment Types of None and Domain (where I specified the domain as "teiid-security"). When I try to access the WSDL from the Web Services console, I am not being prompted for a username and password; I am just being denied (403). I've tried clearing the browser cache and bouncing the server. I'm attaching the datasource and WAR files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
23
0 / 0

[JBoss JIRA] (TEIID-247) Add support for array types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-247?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-247: -------------------------------------- As part of TEIID-2166, tied together the existing array/vararg logic introduced in TEIID-2111. Still need to address array serialization and whether to introduce a fronting ArrayType class similar to lob handling. As for exposing for general use we would still need driver support, better serialization/sizing, limitations on array sizes, parser syntax for array creation and pushdown support. We'll probably address each on an as needed basis rather than treating this as a one shot feature. > Add support for array types > --------------------------- > > Key: TEIID-247 > URL: https://issues.jboss.org/browse/TEIID-247 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Driver, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Original Estimate: 1 week > Remaining Estimate: 1 week > > Add language support for array types. Push down and client support should also be added. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2179) User defined aggregate function return type is ignored

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2179: ------------------------------------- Summary: User defined aggregate function return type is ignored Key: TEIID-2179 URL: https://issues.jboss.org/browse/TEIID-2179 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 The resolver is using the type of the first argument rather than the declared return type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
1
0 / 0

[JBoss JIRA] (TEIID-2178) aggregate functions fails with subquery argument

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2178: ------------------------------------- Summary: aggregate functions fails with subquery argument Key: TEIID-2178 URL: https://issues.jboss.org/browse/TEIID-2178 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 If a subquery is used as an argument to a aggregate function - max((select...)) - the subquery is not planned and will fail to execute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] (TEIID-2157) Need ability to push down LIMIT clause to Sybase

by Van Halbert (JIRA)

Van Halbert created TEIID-2157: ---------------------------------- Summary: Need ability to push down LIMIT clause to Sybase Key: TEIID-2157 URL: https://issues.jboss.org/browse/TEIID-2157 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 7.7.1 Reporter: Van Halbert Assignee: Johnathon Lee Fix For: 7.7.1 Want to add the ability to push down LIMIT clause to Sybase, but it is not supported as of now, becasue the LIMIT translation capability is disabled. SybaseExecutionFactory#supportsRowLimit returns false and it is hard-coded. If it returns true, EDS can push down LIMIT to Sybase translating it to TOP clause, since SybaseExecutionFactory has translateLimit method which translate the LIMIT to TOP clause. The customer want a property which can be switched on the limit translation easily than writing java code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
11
0 / 0

[JBoss JIRA] (TEIID-2169) Buffer Manger's memory should be backed by Infinispan Cache

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2169: ----------------------------------- Summary: Buffer Manger's memory should be backed by Infinispan Cache Key: TEIID-2169 URL: https://issues.jboss.org/browse/TEIID-2169 Project: Teiid Issue Type: Feature Request Components: Query Engine, Server Reporter: Ramesh Reddy Assignee: Steven Hawkins Currently the buffer manager uses the memory from the local VM's heap for processing the intermediate query results, anything that overruns is saved on the disk. Using this model so far proven very efficient. However, when it comes to using the data grid as unlimited temp backing store where the results can be shared with other nodes in the case of fail-over of the session, this in current model does not work. By using the infinispan's local cache in standalone and replicated cache in distributed node for the buffer manager these issues can resolved. Issues may be, currently Buffer Manager uses efficient btree based index store, also the uses file storage in block. To make it work, Teiid needs to have access to the Infinispan's eviction queue and may also needs to implement the cache store. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] (TEIID-2167) Permissions should also specify object type

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2167: ------------------------------------- Summary: Permissions should also specify object type Key: TEIID-2167 URL: https://issues.jboss.org/browse/TEIID-2167 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Teiid permissions only specify a resource name. However it is possible to have to have conflicting schema/table (since we are using non-sql safe unquoted names) or table/procedure names. Ideally we would use proper sql names (this is true everywhere, not just in permissions) and specify the object type (TABLE, PROCEDURE, SCHEMA, LANGUAGE, FUNCTION, etc.). This would also allow us to have a more standard USAGE permission, rather than something like LANGUAGE, which is used to convey the permission and object type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2012