[
https://issues.apache.org/jira/browse/TINKERPOP3-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP3-710.
-----------------------------------------
Resolution: Fixed
Assignee: Marko A. Rodriguez
This was a bug that was introduced when {{HasNextStep}} became the means of
"choosing." Fixed.
However, I did something really neat because of this. We had {{MapTraversal}},
{{MapTraverserTraversal}}, {{FilterTraversal}}, and
{{FilterTraverserTraversal}}. I realized these are pointless. `GraphTraversal`
simply does this now:
{code}
choose(__.filter(e -> predicate.test(e.get())),trueTraversal,falseTraversal)
{code}
I changed this for all similar steps in {{GraphTraversal}} and deleted the
above {{XXXTraversal}} "helpers."
> choose(Predicate,...) throws UnsupportedOperationException
> ----------------------------------------------------------
>
> Key: TINKERPOP3-710
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-710
> Project: TinkerPop 3
> Issue Type: Bug
> Reporter: Matt Frantz
> Assignee: Marko A. Rodriguez
> Fix For: 3.0.0.GA
>
>
> This is on the 3.0.0.M9-incubating tag.
> {noformat}
> gremlin> g.V().choose({ v -> false }, __.out(), __.in())
> The FilterTraversal can only be used as a predicate traversal
> Display stack trace? [yN]
> {noformat}
> This looks like a regression. I don't see any unit tests for the
> {{Predicate}} form of {{choose}}. I happen to maintain my own regressions
> for this, so I could contribute them. Not sure of the fix though.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
