Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Wed, 9 Feb 2011 11:29:57 +0000 (UTC)
From: "Bart van der Schans (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <1208890789.4887.1297250997515.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1445165636.7186.1296737549323.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (JCR-2877) Extend the consistency check in
 BundleDbPersistenceManager's to fix child-parent relations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-2877?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D129924=
42#comment-12992442 ]=20

Bart van der Schans commented on JCR-2877:
------------------------------------------

We found two distinct cases:
- a parent referencing a child node that no longer exists
- a node of which the parent is missing (these can show up in searches)

In the first case we just remove the reference to the child node. In the se=
cond case we delete the node and all of it's children. This could potential=
ly be a bit dangerous, but in our case we found that these nodes are usuall=
y leftovers from delete actions. Another option could be, but that requires=
 a bit more work, follow the unix analogy of a lost+found folder. So instea=
d of removing them just make them children of a  "special" node.

I have to admit that we have mostly been using 1.5 and with recent 1.5 vers=
ions we see almost no data corruption anymore. There have also been some bu=
gs in our custom extensions with virtual layers which caused some of these =
problems in the past.

We always had great difficulty reproducing the data corruptions. Sometimes =
we found a way to reproduce one, but others times not at all.=20

=20


> Extend the consistency check in BundleDbPersistenceManager's to fix child=
-parent relations
> -------------------------------------------------------------------------=
-----------------
>
>                 Key: JCR-2877
>                 URL: https://issues.apache.org/jira/browse/JCR-2877
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.2.2
>            Reporter: Claus K=C3=B6ll
>            Assignee: Claus K=C3=B6ll
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> It could happen that a child node is not in the ChildNodeEntries of its p=
arent node.
> You will get something like (javax.jcr.ItemNotFoundException: failed to b=
uild path of node1: parentNode has no child entry for node1) if you try to =
retrieve the path from node1.
> We should handle such cases and fix it on consistency check

--=20
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira