[ https://issues.jboss.org/browse/TEIID-2577?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2577: ------------------------------------- Bringing the client semantics to the translation layer is an anti-pattern to me, the connection is needed to either do further work that should have handled before the request got to the translator layer, or based on the current execution further work is needs to be queued. If I am understanding the forum text correctly, the need for temp table arises because they did not want write caching facilities at translator layer, instead the job delegated back to engine to use a temp table. Now to use session scoped temp table we are saying we need the same connection back. It seems like we are driving towards what may be a context aware stateless connector execution to state-full execution. Correct me if I am wrong, but providing this as feature at API level does not seem correct to me. -- 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