jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Schriftman" <schri...@gmail.com>
Subject Re: Excerpts Question
Date Tue, 17 Jun 2008 02:37:29 GMT
Thanks, Marcel.

The errorHandling param didn't do the trick, so I'll try an export/import
and see if I can salvage the good data.

At the moment, I'm more concerned about BundleFsPersistenceManager. I'm
stuck with it for now - are you aware of anything I need to particularly
watch out for, or any precautions I can take to safeguard it? Is there any
plan to transactionalize it in the future? Is it even possible to
transactionalize a FS-based PM? I'm guessing that if it were easy to do, it
would have been done already...

The reason I chose BundleFsPersistenceManager in the first place was because
I must be able to persist the entire repository to a remote device (via a
custom FS) and if I'm not mistaken, BundleDbPersistenceManager makes use of
a combination of configured FS and local storage. Is there another option?


Marc Schriftman

On Mon, Jun 16, 2008 at 3:05 AM, Marcel Reutegger <marcel.reutegger@gmx.net>

> Hi Marc,
> ah, right, only the BundleDbPersistenceManagers come with those two
> parameters. please note that the BundleFsPersistenceManager is not
> transactional and is not a recommended persistence manager for a production
> system.
> there's an errorHandling parameter, that you may try out. It handles cases
> where binary properties are missing.
> <param name="errorHandling" value="IGN_MISSING_BLOBS"/>
> If that doesn't help, then you probably have to manually fix the bundle on
> the file system. Unless someone else knows about a tool that can fix it for
> you.
> regards
>  marcel
> Marc Schriftman wrote:
>> Marcel,
>> Just to be clear - the consistencyCheck/consistencyFix functionality
>> appears
>> to live in BundleDbPersistenceManager and I'm using
>> BundleFsPersistenceManager. I added those parameters to my workspace.xml
>> anyway, and restarted the repository, but there was no obvious change.
>> Regards,
>> Marc Schriftman
>> On Wed, Jun 11, 2008 at 8:10 AM, Marcel Reutegger <
>> marcel.reutegger@gmx.net>
>> wrote:
>>  Hi Marc,
>>> you need to set two parameters in your workspace.xml inside the
>>> PersistenceManager tag:
>>> <param name="consistencyCheck" value="true"/>
>>> <param name="consistencyFix" value="true"/>
>>> on startup, jackrabbit will run a consistency check and fix any
>>> inconsistencies. this should allow the query handler to re-index the
>>> workspace again.
>>> regards
>>>  marcel
>>> Marc Schriftman wrote:
>>>  Marcel -
>>>> I'm on 1.4.4 and I'm using
>>>> org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager.
>>>> I've a lot of data in my repository, and it scares me to think that I
>>>> can't
>>>> rebuild my indexes. What can I do to fix the inconsistency?
>>>> Thanks again for your help,
>>>> Marc Schriftman

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message