Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/818
I think I'm going to have to close this because I can't recreate the
problem with the current information supplied and I don't want to merge this PR
as-is because it seems like it's just making the issue go away without actually
addressing the root of the issue. As there is a workaround (i.e. drop the
vertex which drops the edges with it) I don't think we have a bad blocker here.
If the issue arises in the future and can be recreated, I'd be happy to re-open
this.
I still feel like there's something multi-threaded at the root of this
somehow, but I can't think of how since you've confirmed that you don't have
anything like that going on. If the issue does stem from multiple threads
modifying some aspect of the TinkerGraph at the same time then this problem
isn't an issue as TinkerGraph is not meant to be thread-safe for mutations.
---
