atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Mestry (JIRA)" <>
Subject [jira] [Commented] (ATLAS-2523) Import relationship, preserving existing GUID
Date Thu, 03 May 2018 16:32:00 GMT


Ashutosh Mestry commented on ATLAS-2523:

Thanks [~grahamwallis] for the details. I get a better understanding of your intent. This
patch is fine as it is. I may have to make a small change at another place where I am assigning
GUID to an entity that is being imported since this patch will make it redundant (not harmful). 

It may be wroth removing these lines as I think it will make the code cleaner.

These are the lines that I will have to remove:

_EntityGraphMapper: line 762_ 


// for import use the relationship guid provided
if (context.isImport()) {
    String relationshipGuid = getRelationshipGuid(ctx.getValue());
    if(!StringUtils.isEmpty(relationshipGuid)) {
    AtlasGraphUtilsV1.setProperty(ret, Constants.RELATIONSHIP_GUID_PROPERTY_KEY, relationshipGuid);



> Import relationship, preserving existing GUID
> ---------------------------------------------
>                 Key: ATLAS-2523
>                 URL:
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Graham Wallis
>            Priority: Major
>             Fix For: 1.0.0
>         Attachments: ATLAS-2523-2018-04-09.patch
> To add a relationship defined externally (in another metadata repository), I want to
be able to add the relationship and maintain the existing GUID.
> This is possible for an entity by performing an import. It does not seem to be possible
for relationships., because the relationship store always generates a new GUID, which overwrites
the existing GUID.

This message was sent by Atlassian JIRA

View raw message