[
https://issues.jboss.org/browse/TEIID-3272?page=com.atlassian.jira.plugin...
]
Shiveeta Mattoo commented on TEIID-3272:
----------------------------------------
On debugging the code, I am seeing that the input to : private int[]
executeTranslatedCommand(TranslatedCommand translatedComm)
is a single batch of multiple records. Is that an incorrect expectation for the method?
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.
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)