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
Now I am trying to add vertices with the same id_property property with the expectation that this won't happen. But janusgraph is creating as many vertices with different ids as I am trying. On retrieving by the same property, I am getting only the latest vertex created but the older vertices still exist (verified using actual vertex ID).
id1 and id2 are the same which is the latest vertex id i.e. createdId2. But createdId1 and createdId2 are different and there is no warning/error. How is the uniqueness being assured here?
Edit: I even tried setting the consistency modifier to LOCK for this index but that also does not help. Although I feel that if unique is explicitly mentioned at the time of creation, the consistency modifier should be automatically set to LOCK.
Database -> Hbase Mini cluster
Janusgraph version -> 0.6.1
Am I missing something or is this expected? My expectation was that the second creation would either overwrite/add the properties to the same vertex with a warning log. Or worst case throw an Error.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have registered a property key and in the same management transaction made it indexed (composite) and unique.
Now I am trying to add vertices with the same id_property property with the expectation that this won't happen. But janusgraph is creating as many vertices with different ids as I am trying. On retrieving by the same property, I am getting only the latest vertex created but the older vertices still exist (verified using actual vertex ID).
id1 and id2 are the same which is the latest vertex id i.e. createdId2. But createdId1 and createdId2 are different and there is no warning/error. How is the uniqueness being assured here?
Edit: I even tried setting the consistency modifier to LOCK for this index but that also does not help. Although I feel that if unique is explicitly mentioned at the time of creation, the consistency modifier should be automatically set to LOCK.
Database -> Hbase Mini cluster
Janusgraph version -> 0.6.1
Am I missing something or is this expected? My expectation was that the second creation would either overwrite/add the properties to the same vertex with a warning log. Or worst case throw an Error.
Beta Was this translation helpful? Give feedback.
All reactions