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

[Ramesh Reddy (Jira)]

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

Ramesh Reddy commented on TEIIDSB-155:
--------------------------------------

In the example, I was only showing this as a SQL client into Infinispan, connecting to an existing cache. The protobuf file as an example. Simple translator for existing cache.

In order to as dynamic cache configuration, I agree this will not work, we would probably need VDB defined like here http://teiid.github.io/teiid-documents/master/content/reference/Infinispan_Translator.html#_defining_the_metadata , "define metadata in ddl" or protobuf classpath discovery. I think protobuf way will also help spring boot developer-centric view too.

For materialization, it looks like there is some more automation needed, somewhere down the toolchain, like in "code generation plugin" to generate the DDL based model and inject the Infinispan data source.

> 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.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)