[
https://issues.apache.org/jira/browse/TINKERPOP3-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998619#comment-14998619
]
Marko A. Rodriguez commented on TINKERPOP3-951:
-----------------------------------------------
This is actually not a "dead simple fix." It requires the use of
{{GraphComputer.Memory}} to create a distributed lock for all {{Barrier}}
steps. Not crazy, just not so easy it should be a fix for 3.1.0. The following
branch {{origin/TINKERPOP3-951}} has the test case the fails in OLAP and passes
in OLTP.
> Barrier steps provide unexpected results in Gremlin OLAP
> --------------------------------------------------------
>
> Key: TINKERPOP3-951
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-951
> Project: TinkerPop 3
> Issue Type: Bug
> Components: process
> Affects Versions: 3.1.0-incubating
> Reporter: Marko A. Rodriguez
> Assignee: Marko A. Rodriguez
> Fix For: 3.1.1-incubating
>
>
> When a {{Barrier}} is called in OLAP, it should force an iteration and not
> just {{TraverserExecutor.toProcessTraversers}}. That is, it should act as if
> the traverser (even if its local) should be message passed.
> This has always existed, we just never had a test case for the situation.
> Dead simple fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
