[jira] [Closed] (TINKERPOP-1846) LambdaRestrictionStrategy not triggering for Lambda scripts

["stephen mallette (JIRA)" <ji...@apache.org>]

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

stephen mallette closed TINKERPOP-1846.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.3.1
                   3.2.7

> 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
>             Fix For: 3.2.7, 3.3.1
>
>
> 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)