You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/11 07:29:00 UTC
[jira] [Created] (IGNITE-11515) MVCC: Make sure that multiple
cursors are handled properly for JDBC/ODBC
Vladimir Ozerov created IGNITE-11515:
----------------------------------------
Summary: MVCC: Make sure that multiple cursors are handled properly for JDBC/ODBC
Key: IGNITE-11515
URL: https://issues.apache.org/jira/browse/IGNITE-11515
Project: Ignite
Issue Type: Bug
Components: jdbc, mvcc, odbc
Reporter: Vladimir Ozerov
Consider the following scenario executed from JDBC/ODBC driver:
1) Open transaction
2) Get a cursor for some large SELECT
3) Close transaction
4) Overwrite some of not-yet-returned values for the cursor
5) Force vacuum
6) Read remaining values from the cursor
Will we get correct result? Most probably no, because we close transaction on commit without consulting to any opened cursors.
Possible solutions:
1) Extend transaction lifetime until all cursors are closed
2) Or close the cursors forcibly and throw proper error message
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)