You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Sarath Subramanian (JIRA)" <ji...@apache.org> on 2017/08/22 23:01:07 UTC
[jira] [Resolved] (ATLAS-1859) Add validation checking around
relationshipDefs
[ https://issues.apache.org/jira/browse/ATLAS-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sarath Subramanian resolved ATLAS-1859.
---------------------------------------
Resolution: Duplicate
> Add validation checking around relationshipDefs
> -----------------------------------------------
>
> Key: ATLAS-1859
> URL: https://issues.apache.org/jira/browse/ATLAS-1859
> Project: Atlas
> Issue Type: Sub-task
> Reporter: David Radley
> Assignee: Sarath Subramanian
>
> When a relationshipDef creation request is attempted, Atlas needs to check:
> - does the endpoint name in the relationship already exist in another active relationshipdef that applies to that type
> - does the endpoint name in the relationship already exist in another attributedef that applies to that type
> The above needs to account for any attributeDefs and relationshipdefs that apply due to type inheritance.
> There is also the case that for supplied models like Hive, there may need to be some mechanism to allow the old forms of composition relationships - that Gremlin queries might relay on. The old forms of relationship instances are implemented by 2 edges - the new form is one edge.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)