[
https://issues.apache.org/jira/browse/ATLAS-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832391#comment-16832391
]
chaitali borole commented on ATLAS-3179:
----------------------------------------
[~api123], Issue which you facing is discussed in ATLAS-1743, It is way Atlas
is designed to update the attributes with when unique attributes matches with
the existing entity. Need to decide
> Default value caused unnecessary update
> ---------------------------------------
>
> Key: ATLAS-3179
> URL: https://issues.apache.org/jira/browse/ATLAS-3179
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 1.0.0
> Reporter: charles shen
> Priority: Minor
>
> If a type has optional attributes and I create a new entity by calling
> createorupdate without specifying those attributes, atlas will assign some
> default values for the attributes, this is fine. But if I call createorupdate
> with the exact same payload, the second entity will be treated as update and
> will not be skipped though the payload is exactly the same, this is incorrect
> to me.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
