[teiid-issues] [JBoss JIRA] (TEIIDSB-155) Infinispan configuration should support a transactional cache

[Steven Hawkins (Jira)]

    [ https://issues.redhat.com/browse/TEIIDSB-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942931#comment-13942931 ] 

Steven Hawkins edited comment on TEIIDSB-155 at 1/7/20 12:33 PM:
-----------------------------------------------------------------

Transactional support should allow us to use the loadnumber / upsert, rather than cache swapping.

However there are a couple of issues.  First is that this logic does not exist in Teiid, so it's untested from our side.

Second caches default to non-transactional, so the operator based cache or a cache created on the fly will by non-transactional.  For things to work both the remote and local sides need to be setup for transactional support.

Lastly providing the transaction manager to the InfinispanConnectionFactory will require reworking the startup sequence wrt the transactionmanager.  Since there's no option for infinispan to use the platform transaction manager, it must use either our adapter or the user supplied transaction manager.  The latter is easy to autowire, but the adapter is created later than the datasources are and is not exposed as a bean.


was (Author: shawkins):
Creating an issue for transactional support - which should allow us to use the loadnumber / upsert, rather than cache swapping.

> 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
>            Priority: Major
>             Fix For: 1.3.1
>
>
> 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)