[
https://issues.apache.org/jira/browse/ATLAS-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774683#comment-16774683
]
ASF subversion and git services commented on ATLAS-3055:
--------------------------------------------------------
Commit 14f0c6707db37ba6e3e575a56228037f8eaa19d0 in atlas's branch
refs/heads/branch-1.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=14f0c67 ]
ATLAS-3055: updated entity create/update to handle relationship attributes
consistently
(cherry picked from commit 18019733f28448458e2cad94f5e67aabd18316be)
> fix entity create/update to handle relationship attributes consistently
> -----------------------------------------------------------------------
>
> Key: ATLAS-3055
> URL: https://issues.apache.org/jira/browse/ATLAS-3055
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-3055.patch
>
>
> Currently an AtlasEntity can have relationship-attributes either in
> 'attributes' or 'relationshipAttribute'. When a relationship attribute is
> present in both, Atlas removes the attribute from 'attributes' and continues
> processing the value in relationshipAttribute. However, if the attribute is
> present only in 'attributes', Atlas doesn't move this value to
> 'relationshipAttribute' - which can result in the attribute to be ignored if
> no first-class attribute with the same name is present in the entity-def.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)