[teiid-issues] [JBoss JIRA] Resolved: (TEIID-1015) Move threading concerns to the engine
[
https://jira.jboss.org/jira/browse/TEIID-1015?page=com.atlassian.jira.plu...
]
Steve Hawkins resolved TEIID-1015.
----------------------------------
Resolution: Done
Plan processing is still single threaded, but can block to release the thread. Pending
other connector changes, connectors can still block based upon the number of connections
in use.
TODO: could fork at unions/joins.
- Now that transaction handling is not through work manager both transactional and
non-transactional queries could fork.
Move threading concerns to the engine
-------------------------------------
Key: TEIID-1015
URL: https://jira.jboss.org/jira/browse/TEIID-1015
Project: Teiid
Issue Type: Quality Risk
Components: Connector API, Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.0
With the JCA changes we need to more threading concerns primarily to the engine. This
move is motivated by transactional connector work needing to execute serially - where the
transaction lock is held by the calling thread (a request workitem thread from DQPCore).
We should also forgo the creation of random xids for request and local scoped
transactions, rather we can just use the TransactionManager directly like with Teiid 6.2.
--
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