[
https://issues.apache.org/jira/browse/ATLAS-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-2092.
-------------------------------------
Resolution: Fixed
Assignee: Apoorv Naik
Fix Version/s: 0.8.2
0.9-incubating
Committed to following branches:
- master: http://git-wip-us.apache.org/repos/asf/atlas/commit/d6d349e5,
http://git-wip-us.apache.org/repos/asf/atlas/commit/a9ca60e3
- branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/76bf88e4
Thanks [~grahamwallis] for tracking the root cause for this difficult issue and
documenting the details. This immensely helped in fixing the issue.
Thanks [~apoorvnaik] for the patch, which turned out to be more involved than
our email discussion earlier.
> Failures following concurrent updates
> -------------------------------------
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Graham Wallis
> Assignee: Apoorv Naik
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: import-nested-txn.patch, Investigations and findings
> relating to concurrent updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a
> result of concurrent graph updates. This in turn leads to failure of queries
> that specify a type such as an edge label used in an attribute that
> references another entity. This problem is known to affect Atlas entity refs
> – which create graph edges that use edge label schema vertices. It is likely
> that it also affects other types in Atlas.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
