[
https://issues.apache.org/jira/browse/JCR-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated JCR-1428:
---------------------------------------
Attachment: jackrabbit-core.JCR-1428-test-improvement.patch
Patch that improves the committed ConsistencyCheckTest from a previous patch to
reduced debug logging and to shutdown and clean the repository after testing.
Repositories are created as temp directories, which is typically
/tmp/jackrabbitXXXX on *nix and C:\Temp under windows. The cleanup avoids
piling up files in that directory when running the test multiple times.
(Against 1.3 branch)
> Add API for selective bundle consistency check (Jackrabbit-specific)
> --------------------------------------------------------------------
>
> Key: JCR-1428
> URL: https://issues.apache.org/jira/browse/JCR-1428
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-core
> Reporter: Alexander Klimetschek
> Assignee: Jukka Zitting
> Fix For: 1.3.4, 1.5
>
> Attachments: jackrabbit-core.JCR-1428-print-node-path.patch,
> jackrabbit-core.JCR-1428-test-improvement.patch,
> jackrabbit-core.JCR-1428-test.patch, jackrabbit-core.JCR-1428.patch
>
>
> Add a jackrabbit-specific API for doing a selective consistencyCheck, ie. on
> single nodes. The current entire-workspace check can be very slow if there
> workspace is large enough. Also it should be easy to write a tool to invoke
> that feature programmatically rather than by configuration + restart (see
> below).
> Existing Implementation:
> The current bundle consistencyCheck feature is enabled by setting a bundle PM
> parameter and restarting Jackrabbit, it will then run upon startup (see
> JCR-972 for the only issue regarding bundle consistency check). This check
> looks for broken parent-child relationships, ie. it will remove any child
> node entries that reference non-existing parent nodes. For non-existing
> parent UUIDs and other problems in bundles it will log those.
> Outlook:
> An advanced consistencyCheck could also check for non-existing version nodes
> and vice-versa (see JCR-630), but this is not the focus of this issue and
> could be a later addition to the API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
