Github user ml86 commented on the issue:
https://github.com/apache/tinkerpop/pull/606
I continued to read the code and it turned auto that my initial assumption
that the traverser split was caused by the use of addEmitToTraversal was wrong.
The split would occur anyway since RepeatStep::doUntil calls
TraversalUtil.test() which always splits the traverser.
This brings me to the question: Are the splits made in TraversalUtil::test,
TraversalUtil::apply and TraversalUtil::applyAll really necessary? As far as I
understand the code the traversal given to those functions would anyway split
if necessary (e.g. a map step). But by always splitting in the 3 mentioned
methods you also do it for e.g. the LambdaFilterStep which does seem
unnecessary and, more importantly, prevents user from accessing/modifying the
original traverser and the corresponding sack.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
