[
https://issues.jboss.org/browse/TEIID-3272?page=com.atlassian.jira.plugin...
]
Shiveeta Mattoo commented on TEIID-3272:
----------------------------------------
I am observing the behaviour of commit after each batch in JDBCUpdateExecution -
executeTranslatedCommand method.
Once a batch is processed, the method has a finally block as below
finally {
if (commitType) {
restoreAutoCommit(!succeeded, translatedComm);
}
}
The restoreAutoCommit performs the commit after an individual batch is processed without
any exceptions as below
try {
if (!exceptionOccurred) {
connection.commit(); // in JbossAs setAutocommit = true does not trigger the
commit.
}
connection.setAutoCommit(true);
This is how a commit is observed after each batch execution.
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)