[
https://issues.jboss.org/browse/TEIID-1585?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1585:
---------------------------------------
I would target this for 7.5. Putting the ExecutionContext in a threadlocal or adding a
new getConnection signature would be easy enough. Any time there is not an associated
query the context would be null. Currently this would only happen with dynamic vdb
metadata loading.
Another approach since you are customizing the translator anyway would be to have
getConnection return null (assuming that you don't need dynamic vdb functionality) and
then take responsibility for connection management in the Execution.
Make payload available in ExecutionFactory.getConnection
--------------------------------------------------------
Key: TEIID-1585
URL:
https://issues.jboss.org/browse/TEIID-1585
Project: Teiid
Issue Type: Feature Request
Components: Connector API
Affects Versions: 7.3
Reporter: Mark Addleman
Assignee: Steven Hawkins
We require user-specific connections to our backend datasources. We pass user
credentials to the translators using the payload but the payload is not available in the
getConnection(Factory f) method. I propose adding public getConnection(Factory f,
Serializable payload) method in ExecutionFactory whose default implementation is to call
getConnection(Factory f).
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira