You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2016/03/30 19:10:25 UTC

[jira] [Assigned] (TINKERPOP-1225) Do a "rolling reduce" for GroupXXXStep in OLAP.

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

Marko A. Rodriguez reassigned TINKERPOP-1225:
---------------------------------------------

    Assignee: Marko A. Rodriguez

> Do a "rolling reduce" for GroupXXXStep in OLAP.
> -----------------------------------------------
>
>                 Key: TINKERPOP-1225
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1225
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.1.1-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>
> {{GroupXXXStep}} in OLAP is able to process traversers up to the first barrier in the reduction. 99% of the time, the first barrier is the last barrier and thus, you get a nice lazy computation which limits the memory footprint.
> Unfortunately, we don't have this luxury in OLAP. Until!!! However, the work that [~spmallette] did to get {{GroupBiOperator}} to serialize with traversals might make it possible for us to merge barriers in the reduction and thus have OLAP and OLTP {{GroupXXXStep}} behave analogously.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)