[jira] [Resolved] (IGNITE-3870) Keeping SQL query result set in off heap tier

["Vladimir Ozerov (JIRA)" <ji...@apache.org>]

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

Vladimir Ozerov resolved IGNITE-3870.
-------------------------------------
    Resolution: Won't Fix

Closing as "Won't Fix", as this proposal doesn't fit to our architecture - we do not want to hold locks on pages for a long time. 

Instead, the result itslef could reside in special memory part, possibly offheap - this is good idea, but definitely out of scope of this ticket.

> 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
>
> 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.4.14#64029)