Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-1846

LambdaRestrictionStrategy not triggering for Lambda scripts

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 3.2.6
    • Fix Version/s: 3.2.7, 3.3.1
    • Component/s: process
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                spmallette Stephen Mallette
                Reporter:
                spmallette Stephen Mallette
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: