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

Steven Hawkins (JIRA) issues at jboss.org
Mon Jan 5 08:52:29 EST 2015


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

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

> The executed method public void execute() throws TranslatorException, recevies each batch one by one, and delegates processing to 
executeTranslatedCommand for each batch which is getting committed by restoreAutoCommit.

That means that your batches are being broken up at a higher level.  Each call to execute represents a single logical source query operation.  If there were a large bulk insert being executed, then executeTranslatedCommand would further break that up into batches as determined by the max prepared insert batch size.  The only way for an operation to span multiple executes is with a global transaction.

What does your user query look like?  How many updates are you trying to process, 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
>         Attachments: batch1.png
>
>
> 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)


More information about the teiid-issues mailing list