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 2018/07/23 21:34:00 UTC

[jira] [Updated] (TINKERPOP-2014) Allow an ability to specify seeding for random methods such as coin, sample and Order.shuffle

     [ https://issues.apache.org/jira/browse/TINKERPOP-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette updated TINKERPOP-2014:
----------------------------------------
    Affects Version/s: 3.3.3
             Priority: Minor  (was: Major)
          Component/s: process

I think this could be a potential configuration of the `GraphTraversalSource`, thus {{g.withSeed(123L).V().order(shuffle).by('name')}} though I wouldn't discount use of a {{with()}} modulator, but that's not as much a part of the core language as we would probably be want. 

{{by()}} is interesting, but perhaps overly flexible and besides it won't work with {{order()|| cleanly as it already accepts that modulator for other configurations.

Think, think, think....

> Allow an ability to specify seeding for random methods such as coin, sample and Order.shuffle
> ---------------------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-2014
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2014
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.3.3
>            Reporter: Sam Rosen
>            Priority: Minor
>
> Currently, all the methods that have non-deterministic behavior such as coin and sample have no ability to set a seed. The ability to set a seed will allow for reproducible and testable behavior as well as more control flow for random processes. If a certain backend does not support seeding, they could simply ignore it. Some possible API changes:
> graph.traversal.V().withSeed(2L).coin(.5)
> graph.traversal.V().sample(3, 0L)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)