atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sarath Subramanian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1419) Entity attribute values are overridden to null when their value is not provided during complete updates
Date Thu, 05 Jan 2017 05:59:58 GMT

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

Sarath Subramanian commented on ATLAS-1419:
-------------------------------------------

Updated the patch to include 'null' assignment during update for primitive types, arrays and
maps. Previously if you update an attribute to 'null', its ignored and old values are persisted.
Fixed in TypedInstanceToGraphMapper.java and DefaultMetadataService.java

Tested the changes using postman, only the attribute specified is updated and the other attribute
values are intact in vertex.


> Entity attribute values are overridden to null when their value is not provided during
complete updates
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-1419
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1419
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.8-incubating
>            Reporter: Suma Shivaprasad
>             Fix For: 0.8-incubating, 0.7.1-incubating
>
>         Attachments: ATLAS-1419.1.patch, ATLAS-1419.patch, ATLAS-1419_0.7-incubating.patch
>
>
> Currently the hooks all use complete entity update APIs which causes values to be overridden
if the hook is not able to provide a value for that attribute. For eg: Asset.description value
is always set to null. This causes attribute updates to be lost 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message