[opencms-dev] Lucene lock index

[Stephan Hartmann]

Well, the code has gone so far that you can register an event listener that
listens on publish events and updates the index.
have a look at the comment in
net.grcomputing.opencms.search.lucene.Backoffice.
So if you publish a project, a folder or just a single file, the index
should be updated for this resources only. You then can remove your cronjob.
I call it very beta though, but feel free to test it.
It would be nice to have a backoffice page with buttons for deleting and
recreating an index. Can you do this?

BYe,
Stephan

----- Original Message -----
From: "Ernesto De Santis" <ernesto.desantis at colaborativa.net>
To: <opencms-dev at opencms.org>
Sent: Thursday, March 04, 2004 7:11 PM
Subject: Re: [opencms-dev] Lucene lock index


> Hi Matt and Stephan
>
> > Stephan added some methods to IndexManager to support updating the
> > index. I don't think they are exposed to CronIndexManager, though.
> >
> > See updateIndexForFile() and updateFile() in IndexManager.
>
> I am seeing the code of IndexManager. It does not seem difficult to add a
> method to do that if the document is not in the index it adds it and if it
> is that it updates it
> Stephen is working in this?
>
> If the answer is no, I can do it.
>
>
> Ernesto.
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev