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

Steven Hawkins (Jira) issues at jboss.org
Tue Jan 14 16:22:26 EST 2020


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

Steven Hawkins commented on TEIIDSB-155:
----------------------------------------

> The protobuf file as an example.

So for things to work with the example, the expectation is that the user is installing the protobuf definition on their own.

> I think protobuf way will also help spring boot developer-centric view too.

To clarify someone providing the protobuf file (which needs classpath loading as well), is more developer centric than defining the Teiid ddl directly?  Are you implicitly assuming that either the protobuf file will exist or that it's easier to create?

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

I'm not worried about automation yet.  The first cut just needs to work.  I'll initially assume that the user is responsible for creating the Teiid ddl or protobuf file (once we have that working for spring boot) to represent the materialization target.

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


More information about the teiid-issues mailing list