You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2020/09/03 12:05:00 UTC

[jira] [Created] (TINKERPOP-2414) Dynamic options for all steps

Stephen Mallette created TINKERPOP-2414:
-------------------------------------------

             Summary: Dynamic options for all steps
                 Key: TINKERPOP-2414
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2414
             Project: TinkerPop
          Issue Type: Improvement
          Components: process
    Affects Versions: 3.4.8
            Reporter: Stephen Mallette


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:

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

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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)