[ https://issues.apache.org/jira/browse/ATLAS-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238443#comment-17238443 ]
Ashutosh Mestry commented on ATLAS-4048: ---------------------------------------- [~madhan] I have modified the steps. My earlier steps were inaccurate. > Import Service: 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 a source cluster, say cl1. > * Create a destination cluster, say cl2. > Steps to duplicate: > # On cl1: Create Business Metadata say bm1. Add 3 attributes to an entity, > say t1. Perform export. > # On cl2: Use Import REST API, perform import on a different cluster, say > cl2. > # On cl1: Edit the entity t1. Remove 2 of the 3 BM attributes. Perform > export. > # On cl2: Perform import. > Expected results: On cl2: Entity t1 will have 1 business metadata attribute. > Actual result: On cl2, Entity t1 contains all 3 attributes from step 1. > *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)