[
https://issues.redhat.com/browse/TEIIDSB-155?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIIDSB-155.
------------------------------------
Fix Version/s: 1.4.0
Resolution: Done
The changes are in for the 7.6 branch and master. There doesn't seem to be any spot
for the docs on the properties on the spring boot side yet. I'll update the Teiid
side with the other issue.
Essentially the changes here are:
* Rework of transaction manager logic so that our adapter is installed as the transaction
manager bean to be picked up by other things.
* There is a new TransactionMode property, which comes straight from infinispan. The user
would set it to NON_XA (1PC) or NON_DURABLE_XA. FULL_XA is not supported.
* When getting/creating a transactional we'll use the the getOrCreateCache method that
takes an xml configuration. The default config specifies the isolation level as
repeatable_read (which is common) and locking as pessimistic - the default of optimistic
is not supported. Some time later if needed we can externalize that config.
* The sasl mechanism is optional as it has a default on the infinispan side. Similarly we
set defaults for the realm and server name.
Infinispan configuration should support a transactional cache
-------------------------------------------------------------
Key: TEIIDSB-155
URL:
https://issues.redhat.com/browse/TEIIDSB-155
Project: Teiid Spring Boot
Issue Type: Enhancement
Components: datasource
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 1.4.0, 1.3.1
Original Estimate: 1 day, 4 hours
Time Spent: 1 day
Remaining Estimate: 4 hours
The configuration should allow for single phase commit and non-recoverable xa. This will
need to change the transaction support on the translator, set the transaction config, and
register a transactionManager lookup that can find the configured transaction manager.
The infinispan operator does not provide a way to configure the transaction support of
the cache, so this may not fully work yet - I'll test to see what happens both with
the default cache and with trying to create one on demand.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)