[ https://issues.apache.org/jira/browse/ATLAS-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168314#comment-17168314 ]
ASF subversion and git services commented on ATLAS-3398: -------------------------------------------------------- Commit 20127459a59fd0a64966046df3a1b0f64363c4f7 in atlas's branch refs/heads/branch-2.0 from Damian Warszawski [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2012745 ] ATLAS-3398: introduced consitency-lock configuration to avoid multiple entities with same unique attribute value Signed-off-by: Madhan Neethiraj <mad...@apache.org> (cherry picked from commit 80efe92630a9198ed4b4c564f6e78c8079045930) > Duplicates for unique attributes > --------------------------------- > > Key: ATLAS-3398 > URL: https://issues.apache.org/jira/browse/ATLAS-3398 > Project: Atlas > Issue Type: Bug > Components: atlas-core > Affects Versions: 2.0.0, trunk > Reporter: Bolke de Bruin > Priority: Blocker > Labels: integrity > Attachments: zrzut_ekranu_2019-09-03_o_10.28.50.png > > > We are seeing issues with entities being added to Atlas with duplicate > "qualifiedName". The guids differ and other attributes do also differ. Below > a graph that shows the distribution over time for duplicates. We have > difficulty determining which one is the right one (as they are different) in > order to clean them up. > We are also not the only ones encountering this as you can in the linked > issue. > We have noticed that Atlas does not use the > [locking|https://docs.janusgraph.org/master/advanced-topics/eventual-consistency/] > mechanism of Janus to prevent this: > > !zrzut_ekranu_2019-09-03_o_10.28.50.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)