Github user okram commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/60#issuecomment-102108619
`RangeGlobalStep` and `TailGlobalStep` could inherit from some abstract
class. However, I think getting `TailGlobalStep` built is best first or else
the PR will be too big and too hard to review. After that studying the two
implementation should yield the generalization. Moreover, both steps are very
similar to `DedupStep` as well. They are like "lazy barriers."
`TraverserMapReduce` is responsible for dealing with the end of a
traversal. It does any final computations like ranging, sorting, etc. And yes,
`TailGlobalStep` would fit there as well. However, I can connect it up to
`TraverserMapReduce` -- its not that hard.
And yes -- `ComputerVerificationStrategy` will need to complain if
`TailGlobalStep` is used mid-traversal. It can only be used as the end step and
thus, its processing relegated to `TraverserMapReduce`.
---
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.
---
