[ https://issues.jboss.org/browse/TEIID-3272?page=com.atlassian.jira.plugin... ] Shiveeta Mattoo edited comment on TEIID-3272 at 1/5/15 8:33 AM: ---------------------------------------------------------------- The whole intent of the configurable batch commit size is to ensure that although we are capable of using the performance benefit offered by batching the SQL statements, we are able to control the atomicity by configuring the "batch count to commit". Few scenarios around expected behaviour : 1. Batch size = 100, Batch count to commit = 2, Input record count = 500 If Batch # 3 has any error, then Batch#1,2 will be committed and whole of Batch # 3 will be rolled back, and no further batches processed. 2. Batch size = 100, Batch count to commit = 5, Input record count = 500 If any failure is last batch # 5, none of the records are committed, as all 500 records are logically one atomic transation 3.Batch size = 100, Batch count to commit = 2, Input record count = 500 Provide user an additional -- continueOnError option. If this option is enabled we will process the erroneous batch till the erroneous record is reached : If Batch#3 has any error, a Savepoint is set at end of Batch#2 and further records pf batch# 3 are executed and committed one by one till the erroneous record is reached and then processing continues after the failed batch. So only error records can be skipped in this case was (Author: shiveeta.mattoo): The whole intent of the configurable batch commit size is to ensure that although we are capable of using the performance benefit offered by batching the SQL statements, we are able to control the atomicity by configuring the "batch count to commit". Few scenarios around expected behaviour : 1. Batch size = 100, Batch count to commit = 2, Input record count = 500 If Batch # 3 has any error, then Batch#1,2 will be committed and whole of Batch # 3 will be rolled back, and no further batches processed. 2. Batch size = 100, Batch count to commit = 5, Input record count = 500 If any failure is last batch # 5, none of the records are committed, as all 500 records are logically one atomic transation 3.Batch size = 100, Batch count to commit = 2, Input record count = 500 Provide user an additional -- continueOnError option. If this option is enabled we will process the erroneous batch till the erroneous record is reached : If Batch#3 has any error, a Savepoint is set at end of Batch#2 and further records pf batch# 3 are executed and committed one by one till the erroneous record is reached and then processing stops. -- This message was sent by Atlassian JIRA (v6.3.11#6341)