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
It looks like the has step is not very consistent when dealing with UUID properties:
When I use has and hasLabel to search for a vertex by the UUID property, I can simply provide a string and it will find me that vertex (second query), but not when starting the traversal with other vertices (first query).
The expected behaviour is that the first query will find me v[4280] as well.
If I make the EntityId property as a string type then the first two queries give me the same results as expected.
I'm using version janusgraph:1.1.0-20241018-025853.872a475 with the berkeley backend, all settings are default, no indices.
The text was updated successfully, but these errors were encountered:
Hi team
It looks like the
has
step is not very consistent when dealing with UUID properties:When I use
has
andhasLabel
to search for a vertex by the UUID property, I can simply provide a string and it will find me that vertex (second query), but not when starting the traversal with other vertices (first query).The expected behaviour is that the first query will find me v[4280] as well.
If I make the
EntityId
property as a string type then the first two queries give me the same results as expected.I'm using version
janusgraph:1.1.0-20241018-025853.872a475
with the berkeley backend, all settings are default, no indices.The text was updated successfully, but these errors were encountered: