You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/08/10 08:14:00 UTC
[jira] [Created] (IGNITE-6020) SQL: client should request first
pages on query execution instead of first cursor read
Vladimir Ozerov created IGNITE-6020:
---------------------------------------
Summary: 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: Bug
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)