-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect path traversal results after adding a node #2964
Comments
Steps to reproduce:We are developing a testing technique to test your GraphDB. We feel sorry that because the database schema and data values are randomly generated by strings, it will cause inconvenience to your reviewing, but we believe the problem does exist.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior:
We construct the following scenario: x equals to count (nodeA -> nodeB) path numbers, where nodeA and nodeB are randomly selected in the graph. Then we add a new nodeC and an edge from (nodeB -> nodeC), then nodeB has a path to nodeC. y equals to count (nodeA -> nodeC) path numbers again. Then y should equal to x.
We generate graph schema and data based on random strings and values. Here is one of our examples that triggered the bug.
MATCH path=(a)-[*]->(b) WHERE ID(a)=3 AND ID(b)=1 RETURN COUNT(path)
returns 2CREATE (n:redundantNode {nodeKey: 'nodeValue'}) RETURN ID(n)
creates a node, returns node id 104MATCH (a),(b) WHERE ID(a)=1 AND ID(b)=104 CREATE (a)-[:Edge]->(b)
creates an edge.MATCH path=(a)-[*]->(b) WHERE ID(a)=3 AND ID(b)=104 RETURN COUNT(path)
returns 1 != 2Actual behavior:
The query 3 returns 1 != 2. Actually we meet this problem several times.
The text was updated successfully, but these errors were encountered: