[ATLAS-1980] Add relationship instance validation to check end point type

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: atlas-core
• Assignee: David Radley
• Reporter: David Radley
• Created: 21/Jul/17 10:18
• Updated: 17/May/18 05:26
• Resolved: 08/Aug/17 23:26

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"
},

• it does not check that the guid of the relationship is actually of the right type. If I create an instance of the above relationships passing 2 GlossaryCategory guids ; it works. This should be rejected.

Issue Links

• is duplicated by: ATLAS-1859 Add validation checking around relationshipDefs