Apache TinkerPop•2y ago

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()

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

4 Replies

spmallette•2y ago

it's going to take a bit to look into something like this. hopefully i (or someone else) can look into it soon

Joyemang33OP•2y ago

Yeah, sorry for the complex query and I have tried my best to reduce it. Maybe we can investigate some automated tools to reduce such test cases next time.😂

spmallette•2y ago

resolution for this item should be tracked in the JIRA: https://issues.apache.org/jira/browse/TINKERPOP-2961

Joyemang33OP•2y ago

@spmallette Many thanks for your response. I agree that the second query is unsolvable and different from the first one. I include this query in Jira to show that such missing exception does not only occur in the case of an empty graph. Regard to the issue in this question: I believe this query is solvable but it returns inconsistent behavior after I rebuild the graph. Could you kindly further investigate on it?

Gaming

Programming

Encounter strange behaviors in "match()" step