You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergi Vladykin (JIRA)" <ji...@apache.org> on 2017/04/10 08:26:41 UTC
[jira] [Updated] (IGNITE-3870) Keeping SQL query result set in off
heap tier
[ https://issues.apache.org/jira/browse/IGNITE-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergi Vladykin updated IGNITE-3870:
-----------------------------------
Fix Version/s: (was: 2.0)
2.1
> Keeping SQL query result set in off heap tier
> ---------------------------------------------
>
> Key: IGNITE-3870
> URL: https://issues.apache.org/jira/browse/IGNITE-3870
> Project: Ignite
> Issue Type: Task
> Components: SQL
> Reporter: Denis Magda
> Assignee: Sergi Vladykin
> Fix For: 2.1
>
>
> With the new off heap storage architectures (IGNITE-3477) it makes sense to improve a part of the system that prepares an SQL query result set in a such a way:
> - result set should consist of wrappers objects that incorporate off heap pointers to fields and values stored off heap;
> - during the time the result set is being sent over the wire we shouldn't move fields and values from off heap to Java heap but rather implement a solution that will allow us to pass an off heap pointer to a sockets output stream. Probably this can be done by leveraging Java's DirectBuffers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)