As an interim solution when using the Nutch front end, what we did is generate the new index in a temporary folder. Then our script (Ant actually) would turn off the web server (Tomcat in our case) to free the existing index from the Nutch bean, and do a quick switcheroo using OS rename commands. Then restart web server and the old index is deleted.
The outage time would be less than a second, but I agree with you that this is not a great solution. We are not entirely happy with the way Nutch forces you to build a new index each time instead of incrementally changing an existing index, and are interested in writing a modification to handle this better (subject to our other scheduled work). We would be happy if you are interested in collaborating on this. Best regards, Alan _________________________ Alan Tanaman iDNA Solutions -----Original Message----- From: Justin Hartman [mailto:[EMAIL PROTECTED] Sent: 02 January 2007 10:42 To: nutch-user@lucene.apache.org Subject: Re: fetcher : some doubts On 1/2/07, Sean Dean <[EMAIL PROTECTED]> wrote: > You need to delete the old index before you re-index when working within the same directory structure > This is the procedure I follow, which is pretty much what your doing. This assumes you already have at least one active segment and index. Edit as needed. Thanks for the prompt and efficient response - it is much appreciated. The procedure seems fine to me with the exception of having to delete the index before re-indexing. While in a test environment I don't mind this but what happens when I go into a production state. I can't delete the index as people will have nothing to search for while the index is being re-built. Is there another way of doing this or am I missing the plot here big time? -- Regards Justin Hartman PGP Key ID: 102CC123
