[
https://issues.apache.org/jira/browse/ATLAS-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238425#comment-17238425
]
Madhan Neethiraj commented on ATLAS-4048:
-----------------------------------------
[~umesh.padashetty] - classifications and business-metadata attributes of an
entity are not modified during REST API call to update the entity. Allowing
this could cause unintentional removal of classifications and business-metadata
- as API client's are likely to deal only with attributes that are known when
the client was developed; hence wouldn't know about classifications and
business-metadata which could be dynamically added to entities.
Note that if REST API call creates an entity, provided classifications and
business-metadata will be assigned to the entity - as there is no risk of
removing existing value.
Also, note that import operation replaces classifications and business-metadata
on entities with the values specified in the import file. This is an expected
behavior.
> Entity Creation: Updates to Business Metadata
> ---------------------------------------------
>
> Key: ATLAS-4048
> URL: https://issues.apache.org/jira/browse/ATLAS-4048
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 2.1.0
> Reporter: Umesh Padashetty
> Assignee: Ashutosh Mestry
> Priority: Major
> Attachments: ATLAS-4048-Entity-Update-Businessmetada-changes.patch
>
>
> *Background*
> Business Metadata attributes provide a simple way to augment attributes to
> existing entity types.
> Updating Business Metadata for existing entities via REST APIs did not happen
> as the changes were not tracked when considering entity for update.
> *Steps to Duplicate*
> Setup:
> * Create Business Metadata and add 3 attributes.
> Steps to duplicate:
> # Via REST API, create an entity with 3 Business Metadata attributes.
> # From the web UI, load the entity where attributes have been added.
> # Delete 1 attribute.
> # Use entity update REST API to update the entity from step 1.
> Expected results: Entity will have all 3 attributes.
> Actual result: Entity will contain only 2 attributes that were present in
> step 2.
> *Root Cause*
> During entity creation flow, the Business Metadata attributes are not
> considered when detecting if entity has changes.
> Solution: Add a step to detect changes to Business Metadata attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
