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/10/12 20:25:20 UTC
[jira] [Closed] (TINKERPOP-1500) and/or infix and choose() do not
work correctly.
[ https://issues.apache.org/jira/browse/TINKERPOP-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marko A. Rodriguez closed TINKERPOP-1500.
-----------------------------------------
Resolution: Fixed
Assignee: Marko A. Rodriguez
Fix Version/s: 3.2.3
This was a trivial fix. {{ConnectiveStrategy}} simply needed {{HasNextStep}} registered with the other "boundary steps." I added a test case to {{ChooseTest}} which demonstrates proper functioning. I did this while merging /testing the Gremlin Python work from [~aholmber] -- thus, its not an issue branch. CTR.
> and/or infix and choose() do not work correctly.
> ------------------------------------------------
>
> Key: TINKERPOP-1500
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1500
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.2.2
> Reporter: Marko A. Rodriguez
> Assignee: Marko A. Rodriguez
> Fix For: 3.2.3
>
>
> The fragment below works as expected.
> {code}
> choose(and(has("name"), out('knows')), ...)
> {code}
> However, the next fragment doesn't.
> {code}
> choose(has("name").and().out('knows'), ...)
> {code}
> The problem is that {{ConnectiveStrategy}} doesn't treat the {{HasNextStep}} injected by {{choose()}} correctly. The bigger issue is "why do we have a {{HasNextStep}}?! Retarded. We just need to wrap the predicate traversal in a {{filter()}}. ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)