[
https://issues.jboss.org/browse/TEIID-3272?page=com.atlassian.jira.plugin...
]
Shiveeta Mattoo commented on TEIID-3272:
----------------------------------------
Thanks Steven. I understand now, that there's a gap in the way the batches are being
sent vs how they are expected to execute by the executeTransalatedCommand method.
However my request still remains due to following reasons -
1. If I have millions of rows being updated, how could I send such a huge update request
in one one batch command, expecting executeTranslatedCommand to break it down for me.
Since there would be a limit on what we can hold in memory, we would be restricted on this
front.
2. Secondly, since we are setting the autocommit property for the connection to false,
wouldnt it be better, if the control for Commit , is exposed to the caller. In this case,
if we have the control over the "autocommit" property for the connection, we
could send the batches as we desire and yet control the commit as per requirement.
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)