[jira] [Updated] (IGNITE-5397) JDBC thin driver: clear server cursor automatically when last result piece is transmitted
[ https://issues.apache.org/jira/browse/IGNITE-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5397: Component/s: (was: sql) jdbc > 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: jdbc >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.4.14#64029)
[jira] [Updated] (IGNITE-5397) JDBC thin driver: clear server cursor automatically when last result piece is transmitted
[ https://issues.apache.org/jira/browse/IGNITE-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5397: Labels: performance (was: important performance) > 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: Taras Ledkov > 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)
