[teiid-issues] [JBoss JIRA] (TEIIDSB-162) Operator does not account for the transaction manager

[Ramesh Reddy (Jira)]

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

Ramesh Reddy edited comment on TEIIDSB-162 at 1/22/20 7:57 PM:
---------------------------------------------------------------

Added the code in the master and as well in 7.6.0.1.x branches. Please note the image in quay.io with 0.1.0 tag does not have this update, 0.2.0 does, and master is moved 0.2.0 to start new community iteration.

Wanted to move this JIRA to TEIIDTOOLS but this is sub-task the JIRA system did not allow me to do that


was (Author: rareddy):
Added the code in the master and as well in 7.6.0.1.x branches. Please note the image in quay.io with 0.1.0 tag does not have this update, 0.2.0 does, and master is moved 0.2.0 to start new community iteration.

> Operator does not account for the transaction manager
> -----------------------------------------------------
>
>                 Key: TEIIDSB-162
>                 URL: https://issues.redhat.com/browse/TEIIDSB-162
>             Project: Teiid Spring Boot
>          Issue Type: Sub-task
>          Components: OpenShift
>            Reporter: Steven Hawkins
>            Assignee: Ramesh Reddy
>            Priority: Major
>             Fix For: 1.4.0, 1.3.1
>
>
> If you define a vdb in a cr, the generated vdb will just use the platformtransactionmanager. 
>  Since the materialization procedures use transaction blocks, we need a full transaction manager.  By default with the platformtransactionmanager it will throw an exception - only spring managed transactions ...
> The workaround would be to add snowdrop to the cr dependencies, but it would be nice to either always use that in the generated, or detect materialization is being used, or address TEIIDSB-109



--
This message was sent by Atlassian Jira
(v7.13.8#713008)