[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=13948601#comment-13948601 ] 

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

> To clarify someone providing the protobuf file (which needs classpath loading as well), is more developer centric than defining the Teiid ddl directly? 
IMO, providing a protobuf file more developer-centric than providing DDL. I would expect VDB user to define the DDL for their materialization, they should not care about the target environment in terms of the definition of it. This approach holds good even for say materializing to PostgreSQL.

> Are you implicitly assuming that either the protobuf file will exist or that it's easier to create?
For typical Infinispan "as a" data source, yes, I am expecting the protobuf to be registered in the cache, this is similar to DV expectations with databases. In DV we only create the protobuf underneath automatically when DDL is present on model, and it is transparent to the user. 

For developer-centric view, there are couple options we can follow (neither are implemented)
* We can take a look at entity annotations and generate the correct DDL on VDB thus in-turn can generate the protobuf.
* Ask the user to supply the protobuf file as part of data source definition.

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