Looking at what I wrote, yes, it will not be acceptable for a production
environment.
What I failed to mention is that I copy the completed crawl directory somewhere
else, and point Tomcat to look there instead via nutch-site.xml.
When you completed all those steps, and have your new index and segment created
just copy them over what you presently have and do a hot-restart of the web
application. This can be done by "touch"ing the web.xml file in your package.
----- Original Message ----
From: Justin Hartman <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, January 2, 2007 5:41:51 AM
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
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nutch-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-general
