[
https://issues.apache.org/jira/browse/ATLAS-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119071#comment-16119071
]
Sarath Subramanian commented on ATLAS-1983:
-------------------------------------------
added link to review board.
> Relationship instance creation does not police cardinality
> ----------------------------------------------------------
>
> Key: ATLAS-1983
> URL: https://issues.apache.org/jira/browse/ATLAS-1983
> Project: Atlas
> Issue Type: Bug
> Reporter: David Radley
> Assignee: David Radley
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
