[
https://issues.jboss.org/browse/TEIID-3272?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3272:
---------------------------------------
This is how a commit is observed after each batch execution.
But the batch loop is nested within that try finally. So only after all batches have been
processed will the commit occur. Are you sure you aren't seeing a scenario where the
batching is being broken up at a higher level? Also note that the max batch size only
affects prepared inserts.
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)