[jira] [Updated] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes

["Madhan Neethiraj (JIRA)" <ji...@apache.org>]

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

Madhan Neethiraj updated ATLAS-2928:
------------------------------------
    Fix Version/s:     (was: 1.2.0)

> Namespace entity relationship-attribute names to avoid conflict with entity attributes
> --------------------------------------------------------------------------------------
>
>                 Key: ATLAS-2928
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2928
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 1.0.0, 1.1.0
>            Reporter: Madhan Neethiraj
>            Assignee: Le Ma
>            Priority: Critical
>             Fix For: trunk
>
>
> Apache Atlas 1.0 introduced relationships as first-class types. A relationship effectively 'injects' an attribute on the entities at each end. For example, assignment of a glossary term to an entity is captured by relationship AtlasGlossarySemanticAssignment (in 0000-Area0/0011-glossary_model.json). This relationship adds following attributes:
> - Referceable.meanings: set<AtlasGlossaryTerm>
> - AtlasGlossaryTerm.assignedEntities: set<Referenceable>
> This works fine as long as the entity-types involved in the relationship, or their sub-types don't have an attribute with the same name as the attribute injected by the relationships. Once such instance was reported by [~bolke], about relationship attribute DataSet.schema introduced by avro_schema_associatedEntities - which conflicts with spark_table.schema, since spark_table type is a sub-type of DataSet.
> Such name conflicts can be avoided by prefixing relationship-attribute names with a prefix like "r:".



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