[ATLAS-1983] Relationship instance creation does not police cardinality

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Assignee: David Radley
• Reporter: David Radley
• Created: 22/Jul/17 21:00
• Updated: 18/May/20 04:24
• Resolved: 18/May/20 04:24

Description

Using a model RelationshipDef that is defines
{
"name": "CategoryAnchor",
"typeVersion": "1.0",

"endDef1":

{ "name": "categories", "type": "Glossary", "cardinality":"SET", "isContainer":true }

,
"endDef2":

{ "name": "anchor", "type": "GlossaryCategory", "cardinality":"SINGLE" }

,
"relationshipCategory":"COMPOSITION",
"propagateTags":"NONE"
},

• I can create a relationship then add the same GlossayCategory to another glossary. Both edges then exist. There should be only one allowed due to the RelationshipDef cardinality. This should be rejected.

Issue Links

• links to: Review Board