[
https://issues.apache.org/jira/browse/TINKERPOP-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184757#comment-16184757
]
ASF GitHub Bot commented on TINKERPOP-1792:
-------------------------------------------
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/723
Nice set of tests.
VOTE: +1
> Random TraversalSource Selection in GremlinScriptEngine
> -------------------------------------------------------
>
> Key: TINKERPOP-1792
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1792
> Project: TinkerPop
> Issue Type: Bug
> Components: groovy, python
> Affects Versions: 3.2.6
> Reporter: stephen mallette
> Priority: Critical
> Labels: deprecation
>
> {{GremlinScriptEngine}} implementations make a random {{TraversalSource}}
> selection when processing lambdas. Obviously it should be bound more clearly
> to the specific {{TraversalSource}} the caller requests. Another issue that
> isn't completely clear is that bindings passed from the client share the same
> namespace as {{TraversalSource}} bindings which means that if the
> {{TraversalSource}} is "g" then you couldn't write a traversal like:
> {{withSideEffect(“g”, “hello”)}}. That could be smarter as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
