wish of those help Yes, you must annotate the roles in the Actor entity. If you're using neo4j-ogm 1.1.3 or an earlier version, make sure that when you create the new role, you add this to the collection of roles in the Actor entity.
I hope this helps you . MicTech is right. A RelationshipEntity is represented by an edge in the graph, not a node, and currently Repository implementations are applicable only for objects which can be persisted as nodes. This should not cause you any problems.
"EntityNotFoundException: Unable to load RELATIONSHIP with id" when saving RelationshipEntity (with huge gener
To fix the issue you can do I think I somehow solved this with the following steps: Replaced saving the RelationshipEntity with saving the modified NodeEntity Making such modifying operations sequential (previously this could happen in parallel) Encapsulate the modifying operation in a transaction Fixed a bug where in the same transaction the same entity was saved twice (without changing again in the meantime) Fetching the entity again at the beginning of the transaction in order to have the latest state available
hope this fix your issue As always it depends ... And in this case it depends on what you intend to do with the comments. Are they themselves an entrypoint into your graph ? Do you intend to search on the content ? Do you intend to find all the comments in a specific timeframe ? If so it definitely makes sense to have the comments as nodes.