RelationshipEntities between two nodes are dropped after one of the nodes is updated [DATAGRAPH-357]

[spring-projects-issues]

George Agiasoglou opened DATAGRAPH-357 and commented

Hi there,

I have some strange behaviour, please correct me if I am doing something wrong. I am using 1.8.2 enterprise version, embedded in java app. Also using spring 3.2.2.RELEASE and spring-data-neo4j 2.2.0.RELEASE

Scenario:
NodeA, NodeB are of type NodeEntity and Association is of type RelationshipEntity
Create multiple Associations of the same type between NodeA and NodeB.
Save NodeA in NodaARepository, save NodeB in NodeBRepository and all Associations in AssociationRepository
NodeA has got a Set<Association> associations field
Then get NodeA from NodeARepository and edit one of its fields and save. Inspect the saved NodeA object.

Expected result:
Field is updated and the Set contains the right number of associations

Actual result:
Field is updated but the Set does not contain all associations

---

Affects: 2.1.RC2

Attachments:

• code.txt (2.55 kB)
• pom.xml (11.60 kB)

2 votes, 5 watchers

[spring-projects-issues]

Michael Hunger commented

SDN by default only supports one relationship of a type between the same two entities, there is a workaround for that using template.createRelationshipBetween() with the duplicate parameter set to true.

We plan to add a separate flag to @RelatedTo(Via) that allows this behavior too but then cannot work with Sets anymore as the re will be duplicate end-nodes with @RelatedTo

[spring-projects-issues]

Nicolas Mervaillie commented

In order to give users a better vision of what’s happening on SDN, we are bulk closing several issues because they are no more relevant, or related to old and un-maintained SDN versions.
We tried to keep the issues that are still relevant, like feature requests that are still absent from SDN. However, some may have been closed by error. If so, please feel free to reopen.