[
https://issues.jboss.org/browse/TEIID-1323?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1323:
----------------------------------
Fix Version/s: (was: 8.0)
Looked at implementing this. It is more involved than it seems since the planner
currently doesn't check pushdown for parameters and quite a few paths assume that
parameters will be evaluated. The workaround is to use a scalar subquery that selects the
desired value, which is less than ideal since it needs to reference a source table and
issues a separate source query for each argument. This can also be implemented in a
non-breaking fashion (at least from an api perspective - there would still be cases where
custom translators would expect literals, but get Expressions) by just adding a
get/setValue to Argument that use Expressions. Because of the workaround and that this is
not necessarily a breaking change pulling out of 8.0
Add support for pushdown of non-literal procedure parameter
expressions.
------------------------------------------------------------------------
Key: TEIID-1323
URL:
https://issues.jboss.org/browse/TEIID-1323
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
We are forcing all push-down procedure arguments to be literals (for simplicity), when
all expressions should be allowed.
--
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