Using Frames Adjacency "set" method causes orphaned edge references on the vertex

[allanmoso]

When using tinkerpop Frames, we noticed that there were warning messages on our logs:

Record (%s) is null

We realized that this starts appearing after an adjacency is overwritten using a set method annotated with tinkerpop frames' @Adjacency.

While debugging the AdjacencyAnnotationHandler here's what I learned:

• The set method is a combination of two operations: remove all the edges (of that specific label) from the vertex, and then add the new edge.
• Ultimately, the OrientEdge.remove is called which deletes the edge as well as remove the references from both the out and in vertex associated to the edge from their corresponding ORidBag (references are replaced with tombstone markers).
• The problem that I've seen is that after the remove operation the original Vertex instance (in the AdjacencyAnnotationHandler) still has the references to the deleted edges.
• When the addEdge operation happens, I believe, it is overwriting the state of the vertex.

Let me know if I can help with providing more information.