[TINKERPOP-951] Barrier steps provide unexpected results in Gremlin OLAP

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0-incubating
• Fix Version/s: 3.2.0-incubating
• Component/s: process
• Assignee: Marko A. Rodriguez
• Reporter: Marko A. Rodriguez
• Created: 10/Nov/15 01:33
• Updated: 04/Mar/16 18:22
• Resolved: 04/Mar/16 18:22

Description

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.