August 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2039) Virtual table mapping with large number of UNIONs is resulting in excessively long source query

by Marc Shirley (JIRA)

Marc Shirley created TEIID-2039: ----------------------------------- Summary: Virtual table mapping with large number of UNIONs is resulting in excessively long source query Key: TEIID-2039 URL: https://issues.jboss.org/browse/TEIID-2039 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7, 7.4.1 Reporter: Marc Shirley Assignee: Steven Hawkins Queries against a virtual table built upon several layers of UNION transformations is resulting in what appears to be a badly formed, excessively long source query (for example, a SQL string over 1 million characters) that results in slow query execution. -- 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

2
7
0 / 0

[JBoss JIRA] Created: (TEIID-669) Support "pass though" SQL commands to sources

by Ramesh Reddy (JIRA)

Support "pass though" SQL commands to sources --------------------------------------------- Key: TEIID-669 URL: https://jira.jboss.org/jira/browse/TEIID-669 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.2.0 Currently there is no mechanism in Teiid, when a query is submitted to a runtime engine that is passed through the query engine unadulterated and unmodified and submitted directly to a source connector. All queries are parsed, optimized, re-written. Some times this limits the functionality in Teiid, when a user would like to execute a query that is very "source" specific. For example Oracle supports lots of Oracle specific functions that are not supported by the SQL spec, to support execution of these in Teiid user need to resort to UDF, which is cumbersome and involves modelling. Another benefit of this is also to pass DDL to sources, currently since Teiid does not support DDL, this is not possible at all. There is no-expectation that these queries are part of any data integration, these are one off queries that enhance user experience with Teiid if they use this feature. Command Payload mechanism is similar system that is used for authentication and authorization needs at the connector level, this feature can use similar techniques or use some custom extension to the language to define a query 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

12 years

6
18
0 / 0

[JBoss JIRA] (TEIID-2069) Optimze add LIMIT clause to SELECT within a Virtual Procedure using Oracle

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2069: ------------------------------------ Summary: Optimze add LIMIT clause to SELECT within a Virtual Procedure using Oracle Key: TEIID-2069 URL: https://issues.jboss.org/browse/TEIID-2069 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7, 7.4.1 Reporter: Johnathon Lee Assignee: Steven Hawkins LIMIT clause is added to Statement being optimized which fails the operation on Oracle OPTIMIZE: CREATE VIRTUAL PROCEDURE BEGIN DECLARE biginteger VARIABLES.t_pk; VARIABLES.t_pk = (SELECT <table>.seq_gen.cpe_seq FROM <table>.seq_gen); SELECT VARIABLES.t_pk AS result; END #################################################### PROCEDURE COMMAND: CREATE VIRTUAL PROCEDURE BEGIN DECLARE biginteger VARIABLES.t_pk; VARIABLES.t_pk = (SELECT <table>.seq_gen.cpe_seq FROM <table>.seq_gen LIMIT 2); SELECT VARIABLES.t_pk AS result; END -- 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
25
0 / 0

[JBoss JIRA] (TEIID-2158) Generate a Rest based service automatically based on deployed VDB

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2158: ----------------------------------- Summary: Generate a Rest based service automatically based on deployed VDB Key: TEIID-2158 URL: https://issues.jboss.org/browse/TEIID-2158 Project: Teiid Issue Type: Feature Request Components: Server Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.2 Currently to enable REST based services on top of the VDB, Designer provides a mechanism for user to define metadata on the procedure and gives hooks to generate Rest service based WAR file to deploy into a application server. To support OpenShift efforts it would be good to provide this functionality out of box, when Teiid is deployed into the JBoss AS (never in embedded). To define a scenario, - user creates a VDB and defines one or more models - then user creates a virtual procedure with following metadata in the options clause REST:METHOD = GET|PUT|POST|DELETE (mandatory) REST:URI = uri (mandatory) REST:PRODUCES = xml|json|text (optional, if omitted will be calculated from procedures return parameter) REST:CHARSET = character set (optional) (ex:US-ASCII, UTF-8 etc. In cases where the binary data is returned this character set will be used to convert) where REST namesspace is defined as SET NAMESPACE 'http://teiid.org/rest' AS REST; - user deploys a VDB - a jax-rs based war is created and deployed automatically at the end of vdb deployment - if vdb is un-deployed, this jax-rs war will also be undeployed Questions? 1) Should this enforce HTTPBasic Auth by default? since Teiid does not have a way define the DDL based metadata this is difficult. 2) Apart from above procedures, does a generic procedure that executes a add-hoc query helpful? The restriction here is the results will be in a pre-defined format not user defined. -- 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, 1 month

2
6
0 / 0

[JBoss JIRA] (TEIID-2172) Load balancing configuration can result in extraneous "invalid session" messages

by Marc Shirley (JIRA)

Marc Shirley created TEIID-2172: ----------------------------------- Summary: Load balancing configuration can result in extraneous "invalid session" messages Key: TEIID-2172 URL: https://issues.jboss.org/browse/TEIID-2172 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.4.4 Environment: Clustered environment with load balancing enabled for the Teiid data source Reporter: Marc Shirley Assignee: Steven Hawkins When set up in a load balancing configuration with "SET NEW INSTANCE" as the check valid connection SQL in the datasource definition, repeated messages indicating an invalid session are created, similar to: 2012-08-24 10:39:58,818 WARN [org.teiid.SECURITY] (New I/O server worker #1-3) Processing exception 'The specified session ID "5Wt/6zzmsLy2" is invalid. It cannot be found in the userbase.' for session R8ZxYqjZzf/S. Exception type org.teiid.client.security.InvalidSessionException thrown from org.teiid.services.SessionServiceImpl.getSessionInfo(SessionServiceImpl.java:315). Enable more detailed logging to see the entire stacktrace. Not sure if this would be a defect in regards to the conditions that are resulting in the messages to be generated (ie, the old session id shouldn't be being reused), or an enhancement to clarify or adjust the log message or priority to indicate whether this will actually affect the query being submitted. -- 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, 1 month

3
16
0 / 0

[JBoss JIRA] (TEIID-1992) Create Connector/Translator to support Infinispan as a data source

by Van Halbert (JIRA)

Van Halbert created TEIID-1992: ---------------------------------- Summary: Create Connector/Translator to support Infinispan as a data source Key: TEIID-1992 URL: https://issues.jboss.org/browse/TEIID-1992 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: Van Halbert Assignee: Van Halbert Create a Connector/Translator in order for Teiid to support Infinispan as a read-only data source on its initial release. Read Only because if someone is building an object cache, the primary means for updating the cache would not be thru relational means. However, if someone is wanting to add an object cache as a disparate data source for data integration for exposing the content, then this connector/translator will enable that. A goal here is to build an object translator framework that can easily plug in other object cache sources. Example, add support for Coherence. There was a Coherence connector/translator already created in the sandbox, for which, it will provide direction for the object translator. -- 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, 1 month

5
18
0 / 0

[JBoss JIRA] Created: (TEIID-1725) ResultSet metadata error with JDBC handled statements

by Steven Hawkins (JIRA)

ResultSet metadata error with JDBC handled statements ----------------------------------------------------- Key: TEIID-1725 URL: https://issues.jboss.org/browse/TEIID-1725 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Using a preparedstatement of SET / SHOW / transaction statements will fail if resultset metadata is requested prior to execution. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1241) Create a WSDL based WS Resource Adapter

by Steven Hawkins (JIRA)

Create a WSDL based WS Resource Adapter --------------------------------------- Key: TEIID-1241 URL: https://jira.jboss.org/browse/TEIID-1241 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 7.2 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.2 The current WS resource adapter was designed for low-level usage, which doesn't even consult a WSDL. It would be good though to update the existing adapter (or introduce a new) to utilize a WSDL. The WSDL would be used to expose the operations through connector metadata, so that the translator could create the corresponding procedures model.service.port.binding.operation(arg...). Import options could be used to limit the import to only particular services/ports. The WSDL based approach would also allow for the CXF configuration to apply to more than a single port and to more easily allow the policy definition for WS security. Additional semantic support for RPC could be considered, but would need to use JAX-RPC -- 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

12 years, 1 month

2
13
0 / 0

[JBoss JIRA] Created: (TEIID-1714) Allow WS calls to set a timeout value

by Steven Hawkins (JIRA)

Allow WS calls to set a timeout value ------------------------------------- Key: TEIID-1714 URL: https://issues.jboss.org/browse/TEIID-1714 Project: Teiid Issue Type: Enhancement Components: XML Connector Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 With the upgrade beyond CXF 2.3, there is a straightforward way to set timeouts: https://issues.apache.org/jira/browse/CXF-2991 The translator (via a new invoke method) and/or the connection factory should have the ability to specify a request timeout. It is quite cumbersome to use CXF configuration for this and is a common need. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] (TEIID-1923) AS7 based Admin Console needed for Teiid

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1923: ----------------------------------- Summary: AS7 based Admin Console needed for Teiid Key: TEIID-1923 URL: https://issues.jboss.org/browse/TEIID-1923 Project: Teiid Issue Type: Task Components: AdminApi, Build/Kits Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Currently there is NO AS7 based console administration for Teiid. It needs one. Currently only solution available is either use CLI or AdminShell or Admin API for managing a Teiid instance. -- 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, 1 month

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2012