You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Version: 1.0.0
Storage Backend: inmemory
Mixed Index Backend: elasticresearch-8.6.0
API/Driver: Gremlin-python 3.2.6
Steps to Reproduce:
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.
The text was updated successfully, but these errors were encountered: