[
https://issues.apache.org/jira/browse/ATLAS-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784150#comment-16784150
]
ASF subversion and git services commented on ATLAS-3065:
--------------------------------------------------------
Commit 5c8445627891f67c806d7dbdd26e8f856c87a106 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5c84456 ]
ATLAS-3065: added type-patch to remove legacy attributes
> Enable relationship typedef update to remove legacy attributes
> ---------------------------------------------------------------
>
> Key: ATLAS-3065
> URL: https://issues.apache.org/jira/browse/ATLAS-3065
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-3065.patch
>
>
> Relationship types support relationship-ends that point to a first-class
> attribute in the entity-type of the end i.e. legacy attribute. For such
> relationship-ends, the associated entity will have the attribute included in
> both 'attributes' and 'relationshipAttributes'.
> For relationships having legacy attributes at both ends, 2 edges will be
> created between the entities in this relationship. This was necessary earlier
> releases (prior to 1.0) due to use of isOwnedRef/inverseRef constraints,
> hence relationship feature was not available then. With introduction of
> relationships it shouldn't be necessary to use legacy attributes; the same
> can be modeled using COMPOSITION relationship.
> To move away from earlier model (of using isOwnedRef/inverseRef), to use
> COMPOSITION relationship, updates to relationshipDef and entitiyDefs for both
> ends will be necessary. This is to track introducing a type-patch named
> REMOVE_LEGACY_ATTRIBUTES, along lines of ADD_ATTRIBUTE, UPDATE_ATTRIBUTE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
