[
https://issues.apache.org/jira/browse/TINKERPOP-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272728#comment-16272728
]
ASF GitHub Bot commented on TINKERPOP-1846:
-------------------------------------------
GitHub user spmallette opened a pull request:
https://github.com/apache/tinkerpop/pull/759
TINKERPOP-1846 Fixed bug in LambdaRestrictionStrategy
https://issues.apache.org/jira/browse/TINKERPOP-1846
Traversals using Lambda scripts were not triggering this strategy. The
strategy expected the word "lambda" in the toString() of the step that held it.
Lambda objects weren't including that word. This is ready for review/feedback.
I'll withhold my vote while tests are running and others have a chance to chime
in as there are other ways this could be resolved.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/tinkerpop TINKERPOP-1846
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/759.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #759
----
commit f5f4a046f211851e901d303c6593975314171e55
Author: Stephen Mallette <[email protected]>
Date: 2017-11-30T14:26:51Z
TINKERPOP-1846 Fixed bug in LambdaRestrictionStrategy
Traversals using Lambda scripts were not triggering this strategy. The
strategy expected the word "lambda" in the toString() of the step that held it.
Lambda objects weren't including that word.
----
> 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)
