Re: Graph corruption?

Kevin Schmidt


See for a discussion on perhaps the same issue you are running into.

Long story short, it appears you have a unique index, but if you are using locking you can end up with duplicates, but using locking slows things down.  If possible, reorganize things or your traversals so you don't rely on the graph to enforce the unique index.


On Mon, Jun 27, 2022 at 1:44 PM Joe Obernberger <joseph.obernberger@...> wrote:
Hi all - I'm seeing this from a recent graph I built:

gremlin> :> g.V(4162).valueMap()
==>{source=[DS_106], sourceName=[GDELTRecord3]}
gremlin> :> g.V(4146).valueMap()
==>{source=[DS_106], sourceName=[GDELTRecord3]}
gremlin> :> g.V(4226).valueMap()
==>{source=[DS_106], sourceName=[GDELTRecord3]}
gremlin> :> g.V(4250).valueMap()
==>{source=[DS_106], sourceName=[GDELTRecord3]}
gremlin> :> g.V().has("source","DS_106")

The graph has an index on source like this:

PropertyKey sourceProperty =
JanusGraphIndex sourceIndex = mgmt.buildIndex("bySourceComposite",
mgmt.setConsistency(sourceProperty, ConsistencyModifier.LOCK);
mgmt.setConsistency(sourceIndex, ConsistencyModifier.LOCK);

How could the graph end up with several vertices with the same source
string?  Still learning graphs...

Thank you!


This email has been checked for viruses by AVG.

Join to automatically receive all group messages.