[
https://issues.apache.org/jira/browse/ATLAS-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773478#comment-16773478
]
ASF subversion and git services commented on ATLAS-3053:
--------------------------------------------------------
Commit e322dfca4bcfbc5688f554537e50ced7572cf535 in atlas's branch
refs/heads/branch-1.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e322dfc ]
ATLAS-3053: updated notification processing to propagate classifications only
when specified
(cherry picked from commit fe1c299ce4387138ec82b0824415949daa93fa6f)
> Update notification processing to propagate classifications only when
> specified
> -------------------------------------------------------------------------------
>
> Key: ATLAS-3053
> URL: https://issues.apache.org/jira/browse/ATLAS-3053
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-3053.patch
>
>
> When a notification results in creation of an entity, Atlas saves the
> classifications given in the notification (as entity didn’t exist in Atlas,
> this is not considered as an update to classifications). Atlas should
> propagate the classifications added here only when "isPropagate" flag is set
> to 'true'. In other cases, the classifications should not be propagated.
> Please note that notifications are meant to ingest metadata from source
> systems, and not an interface to add/update business metadata - such as
> classifications. Add/update/remove of classifications via notifications is
> not supported - except for the new entities created while processing
> notifications. If a notification results in update to an existing entity,
> Atlas ignores classifications in the notification. Changes to classifications
> must be done via appropriate REST API calls.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)