Encounter strange behaviors in "match()" step

Hello! Sorry for bothering you once again.
When I further investigate the problem I post at https://issues.apache.org/jira/projects/TINKERPOP/issues/TINKERPOP-2961?filter=allopenissues.
I found that the result of this query is unstable.

g.V().match(
__.as("n2").out().as("n1"), 
__.as("n2").in().in().in().both().in().as("n1"), 
__.as("n2").both().in().in().as("n3"), 
__.as("n3").in().both().as("n2"), 
__.as("n2").in().in().in().in().both().as("n4"), 
__.as("n2").out().both().in().as("n4"), 
__.as("n3").both().as("n4"), 
__.as("n1").in().both().both().both().as("n5")
).dedup().count()


After creating the graph based on the statements provided in the Jira attachment, I obtained a result. Then, I deleted all the nodes and recreated the same graph. Surprisingly, when I ran the same query again, it returned a different result. This inconsistency in the query results may suggest a potential bug in the schema creation process. I would appreciate any assistance in reproducing and confirming this issue.

Best regard,
Joye
Was this page helpful?