[ 
https://issues.apache.org/jira/browse/IGNITE-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6020:
------------------------------------
    Issue Type: Improvement  (was: Bug)

> SQL: client should request first pages on query execution instead of first 
> cursor read
> --------------------------------------------------------------------------------------
>
>                 Key: IGNITE-6020
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6020
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>             Fix For: 2.2
>
>
> Currently we request first data blocks form server nodes on first cursor 
> access. However, user code might want to execute a query, and access the 
> cursor after some delay, in hope that asynchronous execution will do the 
> trick. 
> For this reason, we should start requesting pages eagerly on "execute" 
> command rather than on cursor access.
> {code}
> try (QueryCursor cursor = cache.execute(...)) { // <-- Should be here
>     ...
>     for (List<Object> row : cursor) {           // <-- But currently here
>         ...
>     }
> }
> {code}



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

Reply via email to