Hi, Setting the Database Session AutoCommit property to false turns off the JDBC Connection's autocommit feature by calling connection.setAutoCommit(false). But regardless of this value PutSQL will commit the transaction after batchsize number of FlowFiles were processed. This means that setting the batch size to 1 results in a similar behavior as the autocommit = true setting.
You can verify whether the autocommit property works in your environment by increasing the batch size and checking the query logs to see how frequently COMMIT is issued. Regards, Denes On Tue, Feb 26, 2019 at 4:37 PM A_Nad <anadka...@seic.com> wrote: > Hi, > > I am using Nifi 1.9.1 and in this version, PUTSQL has been introduced with > Database Session AutoCommit property which can be set to false so that we > can control the commit on the database. But even after setting Database > Session AutoCommit = 'false', data is getting auto committed on the oracle > database. Not sure what is wrong in my processor. I am preparing an insert > statement before the flowfile is fed to PUTSQL > > Below are the properties of putsql - > JDBC Connection Pool - DBCPConnectionPool(set to oracle database) > SQL Statement - No value set > Support Fragmented Transactions - false > Database Session AutoCommit - false > Transaction Timeout - No value set > Batch Size - 1 > Obtain Generated Keys - false > Rollback On Failure - false > > Please help as this is an important feature for us. > > > > > -- > Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/ >
