Skip to content
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

Bug in pattern matching with multiple relations #647

Open
w158937299 opened this issue Jan 19, 2024 · 0 comments
Open

Bug in pattern matching with multiple relations #647

w158937299 opened this issue Jan 19, 2024 · 0 comments

Comments

@w158937299
Copy link

w158937299 commented Jan 19, 2024

Agensgraph version: 2.13.0
Operating system: (Windows 11)
API/Driver: (psycopg2 2.9.7)
Steps to reproduce
6 (2)

As shown in this picture, query 1 aims to return the count of all nodes going out through the "et0" relationship and returning through the "et3" relationship. Neo4j returns 28, while Agensgraph strangely returns a very large value, 2695, because the total number of nodes in the graph is only 100. Query 2 returns the count of nodes going out through the "et0" relationship, and query 3 returns the count of nodes returning through the "et3" relationship. The results of these two queries on both graph database engines are consistent, but we found that the product of the results of queries 2 and 3 equals the result of query 1. From this, we can infer that Agensgraph, when using the above pattern to match multiple relationships, does not consider these relationships simultaneously but matches them separately. Finally, it returns the results in a manner similar to a Cartesian product, leading to a bug.
@w158937299 w158937299 changed the title Bugs in pattern matching with multiple relations Bug in pattern matching with multiple relations Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant