[
https://issues.jboss.org/browse/TEIID-142?page=com.atlassian.jira.plugin....
]
Steven Hawkins resolved TEIID-142.
----------------------------------
Fix Version/s: (was: 9.0)
Resolution: Out of Date
I'm going to mark this issue as out of date. See
http://community.jboss.org/wiki/Multiple1PC for resolutions when using one or more 1PC
resources under a transaction.
There is still an issue here, which would be to specifically force non-XA behavior for
performance - such as 1PC cross source read / write or multiple reads/updates (which could
be something like "BEGIN ATOMIC <translator name>") to the same source in
a procedure. An issue along those lines can be logged when needed.
Introduce a mechanism to allow single source updates without an xa
txn.
-----------------------------------------------------------------------
Key: TEIID-142
URL:
https://issues.jboss.org/browse/TEIID-142
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 9.x
Reporter: Steven Hawkins
Priority: Minor
Defect Tracker #24910: txnAutoWrap = OFF in 5.5 disables the use of local transactions.
This was primarily done to support customers who 1. weren't paying for the
transactional product
2. weren't using an XA connection for an update
The concern of 1 goes away in 5.6 as all customers will have a transactional product.
The secondary concern requires either a connection property that either ignores autocommit
or the generic support of 1 phase commit on connectors supporting update and local
transactions. The latter solution would allow non-XA aware connectors to seem XA aware as
long as all updates went to a single source. Arjuna would also need to be configured to
support the one phase commit optimization.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira