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 2015/04/14 17:22:12 UTC
[jira] [Created] (TINKERPOP3-631) If there is a reducing barrier in
OLAP, let the next stages
Marko A. Rodriguez created TINKERPOP3-631:
---------------------------------------------
Summary: If there is a reducing barrier in OLAP, let the next stages
Key: TINKERPOP3-631
URL: https://issues.apache.org/jira/browse/TINKERPOP3-631
Project: TinkerPop 3
Issue Type: Improvement
Components: process
Reporter: Marko A. Rodriguez
Assignee: Marko A. Rodriguez
Right now, mid-traversal barriers are not allowed.
{code}
gremlin> g.E().has(label,'rated').groupCount().by('stars').order(local).by(valueDecr)
Global traversals on GraphComputer may not contain mid-traversal barriers: GroupCountStep(value(stars))
Display stack trace? [yN]
{code}
This is because the barrier will aggregate to a single value and what machine is that value suppose to then be on? How about the driver machine? Thus, perhaps once a barrier is hit, the remaining steps are executed OLTP? .... its easy to do, but the problem is that it may confuse people as to the level of parallelism.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)