[ATLAS-3065] Enable relationship typedef update to remove legacy attributes

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0, 2.0.0
• Component/s: atlas-core
• Assignee: Madhan Neethiraj
• Reporter: Madhan Neethiraj
• Created: 05/Mar/19 00:42
• Updated: 26/Sep/19 00:38
• Resolved: 19/Apr/19 18:21

Description

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.

Issue Links

• contains: ATLAS-3068 Regression : Removal of ownedRef/inverseRef constraints in hive types causes related entities missing from the response's "attributes"