[ https://issues.apache.org/jira/browse/ATLAS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018275#comment-17018275 ]
ASF subversion and git services commented on ATLAS-3559: -------------------------------------------------------- Commit b07fa3bb8f6cab0dfd3d9119cfcf4184c2c12209 in atlas's branch refs/heads/branch-2.0 from Ashutosh Mestry [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b07fa3b ] ATLAS-3559: Additional attributes (displayName & userDescription) to Asset. > Asset Type Definition: Add attribute displayName & userDescription > ------------------------------------------------------------------ > > Key: ATLAS-3559 > URL: https://issues.apache.org/jira/browse/ATLAS-3559 > Project: Atlas > Issue Type: Improvement > Components: atlas-core > Affects Versions: 2.0.0 > Reporter: Nikhil Bonte > Assignee: Nikhil Bonte > Priority: Major > Fix For: 2.1.0 > > Attachments: > ATLAS-3559-Add-attribute-displayName-in-Asset-typeDe.patch, > ATLAS-3559-Additional-attributes-to-Asset.patch > > > *Background* > Currently _name_ and _description_ get set as part of setting technical > metadata. Example, Hive hook sets these values as part of posting hook > messages. Once this data is available within Atlas, there is no way to > override these attributes. It would not make sense to change these values > since these are set as part of initial ingest. > *Solution* > Add _displayName_ and _userDescription_ to _Asset_ optional attributes. > Later, UI can be developed to let end user update these properties > interactively. -- This message was sent by Atlassian Jira (v8.3.4#803005)