[ 
https://issues.apache.org/jira/browse/ATLAS-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16098097#comment-16098097
 ] 

David Radley commented on ATLAS-1984:
-------------------------------------

As per my dev list comment, I like the way of using an existing attribute as a 
display name; I wonder if we should have display name as a flag on 
AttributeDef, if there were multiples specified  then we could concatinate or 
police to only allow one. This would allow people to create a new attribute 
called displayAttribute if they like or use an existing attribute like name in 
the GlossaryCategory case. It would also mean that classifications, 
relationships and structures could have display names.       

I wonder if the displayName is not specified for Entities, then we could 
default it to the first unique attribute value if there are unique attributes, 
if not then we could default to the qualified name for Referenceables. If we 
wanted we could sample the data values and look for the most unique and use 
that! 

If we do this - I  think that it would make sense to enhance AtlasObjectId to 
show the list of display attributes as well. 

Also i suggest we call AtlasRelatedObjectId, AtlasRelationshipObjectId. I think 
we should just use the word 'relationship' in all namings - and only introduce 
new terminology like 'related' if there is a new meaning we are looking to 
show.   

 

> Use AtlasRelatedObjectId to refer to relationship attributes during 
> create/update/delete of entity
> --------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-1984
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1984
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: trunk, 0.9-incubating
>            Reporter: Sarath Subramanian
>            Assignee: Sarath Subramanian
>
> AtlasObjectId is used to refer to entity attributes referring to another 
> entity.
> hive_table.columns => List<AtlasObjectId>
> hive_table.db => AtlasObjectId
> Change this to use AtlasRelatedObjectId with the following structure:
> class AtlasRelatedObjectId  {
>    String relationshipGuid;
>    String displayText;
>    AtlasStruct relationshipAttributes; 
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to