jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3268) Re-index fails on corrupt bundle
Date Thu, 22 Mar 2012 11:34:22 GMT

    [ https://issues.apache.org/jira/browse/JCR-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235511#comment-13235511

Alex Parvulescu commented on JCR-3268:

Hi Claus, I don't understand what you are saying :)
Is that a question or a suggestion?

It is not currently handled by JCR-2651 because it addresses only NoSuchItemStateException.

In this issue I'm dealing with is an ItemStateException generated by a corrupt bundle.
> Re-index fails on corrupt bundle
> --------------------------------
>                 Key: JCR-3268
>                 URL: https://issues.apache.org/jira/browse/JCR-3268
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: indexing, jackrabbit-core
>            Reporter: Alex Parvulescu
> The re-indexing process should be more resilient, log an error and simply continue with
the next node. It doesn't seem useful to refuse repository startup in this case.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message