jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "arcassis@gmail.com" <arcas...@gmail.com>
Subject Re: Refresh problem
Date Sat, 12 Sep 2009 08:45:41 GMT
Hello Marcel!
I'm mitziuro's collegue. I want to thank you for what you suggested
regarding JR's SearchIndex, it was very helpful !

With this configuration for a workspace's SearchIndex :
<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
            <param name="path" value="${wsp.home}/index"/>
            <param name="textFilterClasses"
            <param name="extractorPoolSize" value="2"/>
            <param name="supportHighlighting" value="true"/>
            <param name="respectDocumentOrder" value="true"/>
our application behaviour was something like this: 1. add a document, 2.
after saving the document, go to document listing, result: newly added
document wasn't there 3. another click on the document
listing page and voila, the document appeared, (sometimes you need to make
2-3 clicks on the document listing page).
So...my conclusion is that, even if text extraction takes longer than the
default extractorTimeout value (100ms), and a new background thread is
started to handler this,  newly added nodes still don't appear. Why is this
happening ? What else is keeping a lock on the node ?

Now, after I have commented out the textFilterClasses parameter from the
SearchIndex element, JR's works fine (I don't see anymore that latency). The
good news are that we don't need in our application for the moment text
extraction. But when we'll do need...the problem will reapear....

All the best,


On Fri, Sep 11, 2009 at 7:07 PM, Guo Du <mrduguo@gmail.com> wrote:

> On Fri, Sep 11, 2009 at 3:05 PM, Marcel Reutegger
> <marcel.reutegger@gmx.net> wrote:
> > that's not quite correct. everything except text extraction is
> > guaranteed to be indexed as soon as the save (or transaction commit)
> > returns.
> Thanks for the knowledge!
> --Guo


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