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 due to exceptional values handling #4220

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

Bug due to exceptional values handling #4220

w158937299 opened this issue Jan 19, 2024 · 0 comments

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:

10

As shown in this picture, query 1 returns the key-value pairs of nodes with the 'p2' property and 'p2' property value not equal to the string 'false'. The node property key-value pairs returned by Janusgraph are far fewer than those returned by Tinkergraph. Query 2 returns the key-value pairs of nodes with the 'p2' property and 'p2' property value not equal to the boolean value false, and it can be seen that the results returned by Janusgraph and Tinkergraph are consistent. By comparing the results of query 1 and query 2 in Janusgraph, we can conclude that Janusgraph treats the string 'false' property value as a boolean value false, leading to this bug.

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