[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 …
[View More]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
[View Less]
12 years, 2 months
[JBoss JIRA] Created: (TEIID-586) Like pushdown handling
by Steven Hawkins (JIRA)
Like pushdown handling
----------------------
Key: TEIID-586
URL: https://jira.jboss.org/jira/browse/TEIID-586
Project: Teiid
Issue Type: Bug
Components: LDAP Connector, Query Engine, Salesforce Connector
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
Both salesforce and ldap like semantics are not the same as SQL. …
[View More]We could capture this with more capabilities supportsLikeCaseSensitive and supportsLikeWildcardSingleCharacter repectively, or another approach would be to allow the connector to generically indicate partial support and have the query engine both push down the conjunct and leave a copy to be applied after the query. With either explicit supports or generic partial support it would only applicable to top level where clause conjuncts.
--
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
[View Less]
14 years
[JBoss JIRA] Created: (TEIID-587) Better pushdown support for exotic joins
by Steven Hawkins (JIRA)
Better pushdown support for exotic joins
----------------------------------------
Key: TEIID-587
URL: https://jira.jboss.org/jira/browse/TEIID-587
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.1.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.2.0
Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like …
[View More]when possible to = and converting outer joins to inner joins. In both cases we would need to not perform the optimization in the first place or convert into an acceptable form prior to pushdown.
The next is that salesforce, while requiring key criteria also allows other criteria in the left outer join on clause (which would be the same as having criteria on the nested relationship query in the salesforce query). With the capabilities as currently defined this would cause the query to not be pushed down. We should consider adding a relational supported join criteria type that requires key criteria but allows for outside criteria. Also we should treat the lack of inner join support to mean that criteria on the inner side of an outer join cannot be pushed.
--
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
[View Less]
14 years