You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "David Kantor (JIRA)" <ji...@apache.org> on 2015/11/06 18:24:11 UTC
[jira] [Created] (ATLAS-289) updateEntity does not remove existing
edge for multiplicity-one reference
David Kantor created ATLAS-289:
----------------------------------
Summary: updateEntity does not remove existing edge for multiplicity-one reference
Key: ATLAS-289
URL: https://issues.apache.org/jira/browse/ATLAS-289
Project: Atlas
Issue Type: Bug
Affects Versions: 0.6-incubating
Reporter: David Kantor
Assignee: David Kantor
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 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
(v6.3.4#6332)