Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 8 Sep 2016 17:56:20 +0000 (UTC)
From: "Dmitriy Setrakyan (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13003640.1473356130000.522744.1473357380806@Atlassian.JIRA>
In-Reply-To: <JIRA.13003640.1473356130000@Atlassian.JIRA>
References: <JIRA.13003640.1473356130000@Atlassian.JIRA> <JIRA.13003640.1473356130329@arcas>
Subject: [jira] [Assigned] (IGNITE-3870) Keeping SQL query result set in off
 heap tire
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 08 Sep 2016 17:56:22 -0000


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

Dmitriy Setrakyan reassigned IGNITE-3870:
-----------------------------------------

    Assignee: Dmitriy Setrakyan  (was: Sergi Vladykin)

> Keeping SQL query result set in off heap tire
> ---------------------------------------------
>
>                 Key: IGNITE-3870
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3870
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Denis Magda
>            Assignee: Dmitriy Setrakyan
>
> 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.4#6332)