[
https://issues.jboss.org/browse/TEIID-669?page=com.atlassian.jira.plugin....
]
Steven Hawkins commented on TEIID-669:
--------------------------------------
Added handling for the teiid:native-query extension metadata property for JDBC source
tables and procedures. This is along the lines as the comment from Feb-2. See the
reference for more, but in short the extension property allows for physical tables to act
as teiid defined views and for physical procedures to do simple parameter substitution
(the native query will look like "select c from g where c1 = $1" to generate a
source query. There is even an option, teiid:non-prepared, to directly bind values into
the sql in rare cases where someone wants to parametrize on a non-bind eligible value,
such as a table name.
This feature should be extended to the other translator types (in order of importance):
salesforce, olap, ldap.
We should still explore end-to-end pass through with an intermediate step of adding
procedure based execution (similar to mdx) for the other sources.
Support "pass though" SQL commands to sources
---------------------------------------------
Key: TEIID-669
URL:
https://issues.jboss.org/browse/TEIID-669
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
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.
--
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