[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
11 years, 11 months
[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
11 years, 11 months
[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
11 years, 11 months
[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
11 years, 11 months