[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 ] Vladimir Ozerov updated IGNITE-3870: Fix Version/s: (was: 2.2) > 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)
[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 ] Vladimir Ozerov updated IGNITE-3870: Fix Version/s: (was: 2.1) 2.2 > 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.2 > > > 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)
[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)
[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 ] Vladimir Ozerov updated IGNITE-3870: Fix Version/s: 2.0 > 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.0 > > > 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)
[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 ] Vladimir Ozerov updated IGNITE-3870: Component/s: SQL > 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.0 > > > 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)
[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 ] Dmitriy Setrakyan updated IGNITE-3870: -- Summary: Keeping SQL query result set in off heap tier (was: Keeping SQL query result set in off heap tire) > 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 >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)
[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 ] Dmitriy Setrakyan updated IGNITE-3870: -- Assignee: Sergi Vladykin (was: Dmitriy Setrakyan) > 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 >Reporter: Denis Magda >Assignee: Sergi Vladykin > > 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)