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

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

GitHub user skalashnikov opened a pull request:

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

    IGNITE-5397: Jdbc thin driver auto close server cursor option

    

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

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

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

    https://github.com/apache/ignite/pull/2095.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 #2095
    
----
commit 8b1526803ecb71b8bfc4187e413d294da2d36a72
Author: skalashnikov <[email protected]>
Date:   2017-06-05T16:27:54Z

    IGNITE-5397: jdbc thin: avoid sending JdbcQueryCloseRequest message 
whenever possible

commit f6b5dc2f468a4ff9424dee62936cf5728b9541aa
Author: skalashnikov <[email protected]>
Date:   2017-06-05T16:59:40Z

    Merge branch 'master' of https://github.com/apache/ignite into ignite-5397

commit 4731f1c828b43e720e315287c7f7b5aa2f51afc7
Author: skalashnikov <[email protected]>
Date:   2017-06-06T10:15:31Z

    IGNITE-5397: Implemented approach with connection property

commit 29e8d7d4e078a9aaf1ccde7967d201a11de3edde
Author: skalashnikov <[email protected]>
Date:   2017-06-06T10:31:55Z

    Merge branch 'master' of https://github.com/apache/ignite into ignite-5397

commit a124e388cebe5947f2d2dca65d4a2625ada2201b
Author: skalashnikov <[email protected]>
Date:   2017-06-06T14:16:46Z

    IGNITE-5397 Fixed multi-page result set iteration. Added test.

commit efb258212c0237e3051a6c328eb3cc9f07f5f1e6
Author: skalashnikov <[email protected]>
Date:   2017-06-06T14:22:04Z

    Merge branch 'master' of https://github.com/apache/ignite into ignite-5397

----


> JDBC thin driver: clear server cursor automatically when last result piece is 
> transmitted
> -----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-5397
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5397
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.0
>            Reporter: Vladimir Ozerov
>            Assignee: Sergey Kalashnikov
>              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.3.15#6346)

Reply via email to