[
https://issues.apache.org/jira/browse/ATLAS-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752028#comment-16752028
]
Madhan Neethiraj edited comment on ATLAS-3037 at 1/26/19 8:54 PM:
------------------------------------------------------------------
Pre-commit test run:
[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/902/|https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/902/]
was (Author: madhan.neethiraj):
Pre-commit test run:
[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/902/|https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/897/]
> Entity-change detection doesn't handle object-id attributes correctly
> ---------------------------------------------------------------------
>
> Key: ATLAS-3037
> URL: https://issues.apache.org/jira/browse/ATLAS-3037
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 1.1.0
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-3037-master.patch
>
>
> While processing entity-update, Atlas skips the update if there are no
> changes present in the incoming entity. The logic to detect the change fails
> for object-type attributes, as the incoming message will have internal-IDs
> while entity stored in Atlas will have proper GUID of the referenced entity.
> Fixing this change-detection can help avoid unnecessary updates to entities -
> and there by improving the performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
