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 caused by the without operator #4218

Open
w158937299 opened this issue Jan 19, 2024 · 1 comment
Open

Bug caused by the without operator #4218

w158937299 opened this issue Jan 19, 2024 · 1 comment

Comments

@w158937299
Copy link

  • Version: 1.0.0
  • Storage Backend: inmemory
  • Mixed Index Backend: elasticresearch-8.6.0
  • API/Driver: Gremlin-python 3.2.6
  • Steps to Reproduce:
    8

As shown in this picture, query 1 returns the number of edges that have the "p2" property and the "p2" property value does not contain 'GhR'. It can be seen that Janusgraph and tinkergraph return different values. Query 2 returns the number of edges that have the "p2" property, and it is observed that the results of the two graph database engines are consistent. Therefore, we believe that there is an issue with the use of the without operator. Subsequently, we use query 3 to return the property key-value pairs of edges that have the "p2" attribute, and the "p2" property value does not contain 'GhR'. We found that Janusgraph only returns edges with "p2" attribute value as True. It can be inferred that Janusgraph has a bug when using the without operator to handle property values of different types.

@w158937299
Copy link
Author

Hello, the bug also occurs when using the neq operator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant