[jira] [Created] (OAK-6857) Lucene unique index should check path validity for uniqueness constraint

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

Chetan Mehrotra created OAK-6857:
------------------------------------

             Summary: Lucene unique index should check path validity for uniqueness constraint
                 Key: OAK-6857
                 URL: https://issues.apache.org/jira/browse/OAK-6857
             Project: Jackrabbit Oak
          Issue Type: Technical task
          Components: lucene
            Reporter: Chetan Mehrotra
            Assignee: Chetan Mehrotra
             Fix For: 1.8


The {{UniquenessConstraintValidator}} currently checks for any new index entry if any matching entry is found in primary (property) and secondary (lucene) index. 

This can lead to false positive where the entry in index is obsolete and due to async index lagging behind is yet not pruned. For e.g. if 

# Time T1 - path /a/@uuid=1 existed , present in lucene index
# Time T2 - path /a removed (async index yet not catched up)
# Time T3 - path /b/@uuid=1 being created. 

In this case save should pass. However as async index has yet not catched up it reports a constraint validation exception. As a fix {{UniquenessConstraintValidator}}  should check if reported paths are valid wrt current revision



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)