stephen mallette created TINKERPOP-2004:
-------------------------------------------
Summary: LazyBarrierStrategy should be the only strategy that adds
barriers
Key: TINKERPOP-2004
URL: https://issues.apache.org/jira/browse/TINKERPOP-2004
Project: TinkerPop
Issue Type: Improvement
Components: process
Affects Versions: 3.2.9
Reporter: stephen mallette
Assignee: stephen mallette
Fix For: 3.4.0, 3.3.4, 3.2.10
As it stands it is hard to reason about {{barrier()}} when you want fine
grained control over the processing of a traversal. In other words if you feel
like preventing barrier injection you can't do it reasonably without removing a
lot of strategies and it isn't trivial to recall which strategies are adding
them. If they were all added by {{LazyBarrierStrategy}} it would be much more
simple to remember.
I suppose a question remains: is there anyway to ensure that future changes
don't undo this work?
I won't say that this is a "breaking" change exactly but a good body of Update
Documentation should be required for this one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
