[TINKERPOP-2414] Dynamic options for all steps

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.4.8
• Component/s: process
• Assignee: Unassigned
• Reporter: Stephen Mallette
• Created: 03/Sep/20 12:04
• Updated: 03/Sep/20 18:53

Description

This issue may be discussed on a separate ticket somewhere already because I feel like it has come up before, but I can't find it immediately. Some steps can base their arguments on the result of `Traversal` and some cannot. This leads to folks trying things like:

g.V().hasLabel('Person').sample(math('4/2'))

and getting an error. Obviously the above is bit of a contrived example but one could imagine modifying the sample size based on some data dynamically gathered in the traversal itself. We could proliferate Traversal overloads everywhere for all steps and make it a rule that they should work that way or perhaps there is a more elegant approach that hasn't been considered yet.