Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Sun, 10 Feb 2013 09:07:12 +0000 (UTC)
From: "Unico Hommes (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12631634.1360487111450.270674.1360487232994@arcas>
In-Reply-To: <JIRA.12631634.1360487111450@arcas>
References: <JIRA.12631634.1360487111450@arcas>
Subject: [jira] [Updated] (JCR-3517) Search index consistency check should
 be able to double check its reported issues
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Unico Hommes updated JCR-3517:
------------------------------

    Issue Type: Improvement  (was: Bug)
    
> Search index consistency check should be able to double check its reported issues
> ---------------------------------------------------------------------------------
>
>                 Key: JCR-3517
>                 URL: https://issues.apache.org/jira/browse/JCR-3517
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>            Reporter: Unico Hommes
>            Assignee: Unico Hommes
>             Fix For: 2.6.1, 2.7
>
>
> In live and busy environments doing a consistency check on the index regularly turns up false positives. For instance when during a concurrent update a node was already inserted into the database but not yet indexed. To make the consistency check more robust against such cases we can add double check capability to the consistency check. This will allow reliable consistency checking and repairing of the index in such environments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira