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/06/02 20:02:59 UTC
[jira] [Closed] (TINKERPOP-1323) ComputerVerificationStrategy fails
for nested match() steps
[ https://issues.apache.org/jira/browse/TINKERPOP-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marko A. Rodriguez closed TINKERPOP-1323.
-----------------------------------------
Resolution: Fixed
Assignee: Marko A. Rodriguez
Fix Version/s: (was: 3.1.3)
This is only fixed in 3.2.1 because that is where all the new work on {{TraversalHelper.isLocalStarGraph()}} was done.
> ComputerVerificationStrategy fails for nested match() steps
> -----------------------------------------------------------
>
> Key: TINKERPOP-1323
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1323
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.2.0-incubating, 3.1.2-incubating
> Reporter: Daniel Kuppitz
> Assignee: Marko A. Rodriguez
> Fix For: 3.2.1
>
>
> A nested {{match()}} can leave the star-graph w/o the compiler complaining about it; this ultimately leads to a {{RuntimeException}}. The most simple query to reproduce it:
> {code}
> g = TinkerFactory.createModern().traversal().withComputer()
> g.V().filter(match(
> __.as("project").in("created").as("person"),
> __.as("person").values("name").as("name")
> ))
> {code}
> Of course the filter step is pointless in this example, but that's the easiest way to reproduce it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)