You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2016/01/12 22:54:39 UTC

[jira] [Closed] (TINKERPOP-1060) LambdaRestrictionStrategy too restrictive

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

Marko A. Rodriguez closed TINKERPOP-1060.
-----------------------------------------
    Resolution: Fixed

> LambdaRestrictionStrategy too restrictive
> -----------------------------------------
>
>                 Key: TINKERPOP-1060
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1060
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: process
>    Affects Versions: 3.0.2-incubating
>            Reporter: Daniel Kuppitz
>            Assignee: Marko A. Rodriguez
>             Fix For: 3.1.1-incubating
>
>
> It seems like {{LambdaRestrictionStrategy}} considers tokens to be lambdas:
> {noformat}
> gremlin> :> g.V().label().groupCount()
> ==>[country:21, product:77, item:2155, employee:9, region:18, category:8, order:830, customer:91]
> gremlin> :> g.V().groupCount().by(label)
> The provided traversal contains a lambda step: LambdaMapStep(label)
> Display stack trace? [yN]
> {noformat}
> Of course tokens aren't simple objects, but I think they should be allowed / considered to be safe, even if the {{LambdaRestrictionStrategy}} is applied.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)