| commit | d8106f7cd3fefe8c979e2f5baccb9d0134f29400 | [log] [tgz] |
|---|---|---|
| author | Stephen Mallette <spmva@genoprime.com> | Sun Aug 30 05:28:14 2020 -0400 |
| committer | Stephen Mallette <stepmall@amazon.com> | Tue Sep 08 08:21:56 2020 -0400 |
| tree | 742fcd614a019b72250d0f3db0a46499324c15ce | |
| parent | 2cea7b2b08359d501730b7bf3cd55d9d80bf4c74 [diff] |
TINKERPOP-2396 Added Traversal.getTraverserSetSupplier() In this way the steps get their TraverserSetSupplier from the Traversal that spawned it which matches a bit with how Traverser objects get generated. This approach seems better than what I had suggested in JIRA where TraversalStrategy implementations might be used.