[
https://issues.apache.org/jira/browse/ATLAS-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308043#comment-16308043
]
Sharmadha Sainath commented on ATLAS-2324:
------------------------------------------
[~grahamwallis] , While creating entity using REST , we provide some negative
value to GUID. After creation , a positive GUID is assigned to the entity by
Atlas. While updating that entity , corresponding GUID should be used.
In my Atlas Instance , GUID "406a4202-90cc-4887-a8e5-e446389e14cb" (GUID
mentioned in put_v1) is generated. So POSTing the same JSON "put_v1" in other
Atlas instance will not work. In other Atlas instance , some other GUID will be
created for entity creation , and that GUID should be used while updating the
entity. I meant this change to be done in the JIRA description.
Please let me know if the explanation was clear .
> Regression : Entity update by PUT using V1 APIs throws 500 Internal server
> exception
> ------------------------------------------------------------------------------------
>
> Key: ATLAS-2324
> URL: https://issues.apache.org/jira/browse/ATLAS-2324
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 1.0.0
> Reporter: Sharmadha Sainath
> Assignee: Madhan Neethiraj
> Fix For: 1.0.0
>
> Attachments: ATLAS-2324.patch, NPE_during_PUT_update.txt, ent_v1,
> put_v1, type_v1
>
>
> Steps to repro :
> 1. Create type using JSON type_v1 by POSTing to /api/atlas/types
> 2. Create entity for the type using JSON ent_v1 by POSTing to
> /api/atlas/entities
> 3. Update the entity using JSON put_v1 (guid to be changed in the JSON) by
> PUTting to /api/atlas/entities.
> Update using PUT using V1 APIs throws NPE.
> Attached the complete exception stack trace .
> in V2 APIs , full entity update is done using POST and not PUT.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
