[teiid-issues] [JBoss JIRA] (TEIID-3272) JDBC Translator | Segregation of batch execution and commit mode

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029587#comment-13029587 ] 

Steven Hawkins commented on TEIID-3272:
---------------------------------------

I may not have followed you completely on the forum posting.  The current behavior is to start a local transaction (assuming there is not a higher level transaction already) and then commit when all batches have been processed - not a commit for each batch.  When are you seeing a commit with each batch?  Is that from a higher level breakdown of source queries?

> The no of batches after which a commit is desired should be a configurable option.

Can you elaborate on the scenarios when you want to have a non-atomic update?  What would be your expectations when there is an exception - stop processing batches, best effort continue, etc.?

> JDBC Translator | Segregation of batch execution and commit mode 
> -----------------------------------------------------------------
>
>                 Key: TEIID-3272
>                 URL: https://issues.jboss.org/browse/TEIID-3272
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: JDBC Connector
>            Reporter: Shiveeta Mattoo
>            Assignee: Steven Hawkins
>              Labels: Batch-Commit, JDBC-Transator
>
> In JDBC Translator, the batch execution and commit are coupled together. Hence, we after every batch execution, a commit is executed. 
> This enhancement is for providing an ability to support the commit after a configurable 'x' no. of batches has completed, instead of an automatic commit after every batch.
> The no of batches after which a commit is desired should be a configurable option.
>  



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)