You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/16 12:07:00 UTC

[jira] [Commented] (IGNITE-5396) ODBC: Clear server cursor automatically when last result piece is transmitted

    [ https://issues.apache.org/jira/browse/IGNITE-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051812#comment-16051812 ] 

ASF GitHub Bot commented on IGNITE-5396:
----------------------------------------

GitHub user isapego opened a pull request:

    https://github.com/apache/ignite/pull/2143

    IGNITE-5396: ODBC: Server cursor automatically cleaned when last result page is received.

    piece is transmitted

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-5396

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/2143.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2143
    
----
commit 3d9e46975be246a3f64e4ee83c7e8eb85b38e28c
Author: Igor Sapego <is...@gridgain.com>
Date:   2017-06-16T12:05:09Z

    IGNITE-5396: ODBC: Server cursor automatically cleaned when last result
    piece is transmitted

----


> ODBC: Clear server cursor automatically when last result piece is transmitted
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-5396
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5396
>             Project: Ignite
>          Issue Type: Task
>          Components: odbc
>    Affects Versions: 2.0
>            Reporter: Vladimir Ozerov
>            Assignee: Igor Sapego
>              Labels: performance
>             Fix For: 2.1
>
>
> When last part of result set is sent from the server, we should do the following:
> 1) Clear server-side cursor
> 2) Set special marker on the client side that "cursor" close request is not needed. This way we will save two network hops for typical DML request.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)