[ 
https://issues.apache.org/jira/browse/ATLAS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj updated ATLAS-1980:
------------------------------------
    Fix Version/s: 1.0.0
      Component/s:  atlas-core

> Add relationship instance validation to check end point type
> ------------------------------------------------------------
>
>                 Key: ATLAS-1980
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1980
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>            Reporter: David Radley
>            Assignee: David Radley
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: ATLAS-1980.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to