[
https://issues.apache.org/jira/browse/IGNITE-11515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin resolved IGNITE-11515.
------------------------------------------
Resolution: Won't Fix
This is not actual anymore due to IGNITE-13871, IGNITE-15760
> 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
> Priority: Major
>
> 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
(v8.20.10#820010)
