atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <>
Subject [jira] [Updated] (ATLAS-289) updateEntity does not remove existing edge for multiplicity-one reference
Date Wed, 09 Dec 2015 14:25:13 GMT


Suma Shivaprasad updated ATLAS-289:
    Fix Version/s:     (was: trunk)

> updateEntity does not remove existing edge for multiplicity-one reference
> -------------------------------------------------------------------------
>                 Key: ATLAS-289
>                 URL:
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.6-incubating
>            Reporter: David Kantor
>            Assignee: David Kantor
>              Labels: patch
>             Fix For: 0.6-incubating
>         Attachments: ATLAS-289-v0.patch,
> updateEntity does not properly update a multiplicity-one non-composite reference, such
that the entity appears to not have been updated when it is retrieved after updateEntity is
> updateEntity is adding an edge from the source vertex to the
> new target vertex, but not removing the existing edge that connects the
> source to the old target.  So after the update completes, the source vertex has 2 edges
for this class reference (which violates the upper bound constraint defined for that attribute
but that constraint is not enforced).  
> When the source entity is retrieved after the update, GraphBackedMetadataRepository.GraphToTypedInstanceMapper.mapVertexToClassReference()
uses whatever edge is returned first by the iterator to set the reference value.  If the first
edge is the "old" edge, the returned entity appears to have not been updated as it is referencing
the original target entity.

This message was sent by Atlassian JIRA

View raw message