[ https://issues.apache.org/jira/browse/TINKERPOP-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP-1491. --------------------------------------- Resolution: Won't Do Given that this idea has been hanging around for a while unimplemented, I'm going to close it - seems like it could be helpful to some graph providers who haven't optimized within/without, but probably not worth the added complexity in tinkerpop. Seems like graph providers should just deal with all aspects of {{P}} > P.within and P.without P.or/P.and optimization > ---------------------------------------------- > > Key: TINKERPOP-1491 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1491 > Project: TinkerPop > Issue Type: Improvement > Components: process > Affects Versions: 3.2.2 > Reporter: Marko A. Rodriguez > Priority: Major > > {{P.within(a,b)}} is equivalent to {{P.or(P.eq(2),P.eq(b))}}. Likewise, > {{P.without(a,b)}} is equivalent to {{P.and(P.neq(2),P.neq(b))}}. > The latter of the two are more readily useful to provider optimizers. Thus, I > think if the arguments to {{within()}} and {{without()}} are less than > (?)5(?), then we express it in {{or()}}/{{and()}}-form. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)