[
https://issues.apache.org/jira/browse/ATLAS-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Kantor updated ATLAS-499:
-------------------------------
Description:
For references that are defined in the type system as bi-directional, Atlas
does not enforce that clients update both sides of the reference, and relies on
well behaved client applications for repository consistency. This allows the
repository to be easily corrupted with unbalanced references. Atlas should
automatically update the inverse reference to avoid this corruption. It also
is a performance optimization, in that clients can update a bi-directional
non-composite reference without retrieving both entities, the only need the
guid for the target entity.
Note that changes are being tracked/applied separately for the V1/legacy and V2
code paths under the sub-tasks.
was:For references that are defined in the type system as bi-directional,
Atlas does not enforce that clients update both sides of the reference, and
relies on well behaved client applications for repository consistency. This
allows the repository to be easily corrupted with unbalanced references. Atlas
should automatically update the inverse reference to avoid this corruption.
> Automatically update inverse references to prevent repository corruption
> ------------------------------------------------------------------------
>
> Key: ATLAS-499
> URL: https://issues.apache.org/jira/browse/ATLAS-499
> Project: Atlas
> Issue Type: Improvement
> Reporter: David Kantor
> Assignee: David Kantor
>
> For references that are defined in the type system as bi-directional, Atlas
> does not enforce that clients update both sides of the reference, and relies
> on well behaved client applications for repository consistency. This allows
> the repository to be easily corrupted with unbalanced references. Atlas
> should automatically update the inverse reference to avoid this corruption.
> It also is a performance optimization, in that clients can update a
> bi-directional non-composite reference without retrieving both entities, the
> only need the guid for the target entity.
> Note that changes are being tracked/applied separately for the V1/legacy and
> V2 code paths under the sub-tasks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
