[
https://issues.apache.org/jira/browse/TINKERPOP-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277476#comment-16277476
]
ASF GitHub Bot commented on TINKERPOP-1846:
-------------------------------------------
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/759
VOTE: +1
> LambdaRestrictionStrategy not triggering for Lambda scripts
> -----------------------------------------------------------
>
> Key: TINKERPOP-1846
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1846
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.2.6
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Critical
>
> Traversals that use {{Lambda}} as described here:
> http://tinkerpop.apache.org/docs/current/reference/#_the_lambda_solution
> for example are not triggering the {{LambdaRestrictionStrategy}}. The problem
> is with the rule for the trigger itself which expects that the word "lambda"
> be in {{toString()}} of the step being evaluated. Currently steps that use
> {{Lambda}} don't produce that in their {{toString()}} - they simply return
> the lambda script. There are multiple fixes to this, but I think the easiest
> might be to just change the {{Lambda.toString()}} to include the word
> "lambda" and then it all just works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
