[ https://issues.apache.org/jira/browse/IGNITE-9947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771099#comment-16771099 ]
Taras Ledkov commented on IGNITE-9947: -------------------------------------- [~pkouznet], [~vozerov]. The test looks like invalid a bit: after the first {{fillParamsWithPerson(pstmt, 1);}} the batch wasn't added. If the {{pstmt.addBatch();}} is added after this line, the second call of the {{addBatch}} throws: {{java.sql.SQLException: Statement has non-empty batch (call executeBatch() or clearBatch() before enabling streaming).}} I guess this is valid behavior because STREAMING mode is Ignite-specific. > JDBC thin: Batch update is not performed if streaming state changed before > executeBatch() > ----------------------------------------------------------------------------------------- > > Key: IGNITE-9947 > URL: https://issues.apache.org/jira/browse/IGNITE-9947 > Project: Ignite > Issue Type: Bug > Components: sql > Affects Versions: 2.6 > Reporter: Pavel Kuznetsov > Assignee: Taras Ledkov > Priority: Major > > Thin driver is affected. > How to reproduce: > 0) Create table > 1) Create PreparedStatement "INSERT INTO TAB VALUES (?, ?)" > 2) Set statement's args and call .addBatch() > 3) Turn on streaming > 4) call .executeBatch() > 5) Turn off streaming to flush streamer. > After that table should contain batched data, but it doesn't -- This message was sent by Atlassian JIRA (v7.6.3#76005)