[jira] [Commented] (ATLAS-2324) Regression : Entity update by PUT using V1 APIs throws 500 Internal server exception

["Graham Wallis (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307898#comment-16307898 ] 

Graham Wallis commented on ATLAS-2324:
--------------------------------------

Just for my education - what's the use case for changing the GUID associated with an entity? I'm sure it is needed, but I have not yet researched/understood the different styles of GUID as seen by comparing ent_v1 and put_v1.
Is this something that happens following an import?
Thanks, Graham

> 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)