[jira] [Updated] (ATLAS-3559) Asset Type Definition: Add attribute displayName & userDescription
[ https://issues.apache.org/jira/browse/ATLAS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3559: --- Summary: Asset Type Definition: Add attribute displayName & userDescription (was: Add attribute 'displayName' in Asset typeDef) > Asset Type Definition: Add attribute displayName & userDescription > -- > > Key: ATLAS-3559 > URL: https://issues.apache.org/jira/browse/ATLAS-3559 > Project: Atlas > Issue Type: Improvement >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Attachments: > ATLAS-3559-Add-attribute-displayName-in-Asset-typeDe.patch, > ATLAS-3559-Additional-attributes-to-Asset.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3559) Asset Type Definition: Add attribute displayName & userDescription
[ https://issues.apache.org/jira/browse/ATLAS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3559: --- Description: *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. was: *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. > Asset Type Definition: Add attribute displayName & userDescription > -- > > Key: ATLAS-3559 > URL: https://issues.apache.org/jira/browse/ATLAS-3559 > Project: Atlas > Issue Type: Improvement >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > 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)
[jira] [Updated] (ATLAS-3559) Asset Type Definition: Add attribute displayName & userDescription
[ https://issues.apache.org/jira/browse/ATLAS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3559: --- Description: *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. > Asset Type Definition: Add attribute displayName & userDescription > -- > > Key: ATLAS-3559 > URL: https://issues.apache.org/jira/browse/ATLAS-3559 > Project: Atlas > Issue Type: Improvement >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > 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)
[jira] [Updated] (ATLAS-3559) Asset Type Definition: Add attribute displayName & userDescription
[ https://issues.apache.org/jira/browse/ATLAS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3559: --- Description: *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. was: *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. > Asset Type Definition: Add attribute displayName & userDescription > -- > > Key: ATLAS-3559 > URL: https://issues.apache.org/jira/browse/ATLAS-3559 > Project: Atlas > Issue Type: Improvement >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > 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)
[jira] [Updated] (ATLAS-3559) Asset Type Definition: Add attribute displayName & userDescription
[ https://issues.apache.org/jira/browse/ATLAS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3559: -- Affects Version/s: 2.0.0 > Asset Type Definition: Add attribute displayName & userDescription > -- > > Key: ATLAS-3559 > URL: https://issues.apache.org/jira/browse/ATLAS-3559 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > 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)
[jira] [Updated] (ATLAS-3559) Asset Type Definition: Add attribute displayName & userDescription
[ https://issues.apache.org/jira/browse/ATLAS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3559: -- Fix Version/s: 2.1.0 > Asset Type Definition: Add attribute displayName & userDescription > -- > > Key: ATLAS-3559 > URL: https://issues.apache.org/jira/browse/ATLAS-3559 > Project: Atlas > Issue Type: Improvement >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)
[jira] [Updated] (ATLAS-3559) Asset Type Definition: Add attribute displayName & userDescription
[ https://issues.apache.org/jira/browse/ATLAS-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3559: -- Component/s: atlas-core > 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)