Maybe We should have a close method also in IndexSearcher
Which gives greater flexibility while deleting files
But even after implemention , the data is locked by some search mechanism
Maybe Some ArrayFileReader is holding it
Are'nt we supposed to release these handlers
Rgds
Prabhu
On 2/1/06, Raghavendra Prabhu <[EMAIL PROTECTED]> wrote:
>
> Hi guys
>
> Even i face the same problem
>
> I am doing something similar to what howie is doing
>
> But i want to delete the existing files in the index and replace them
>
>
> I even implement a new method which calls close.This closes the
>
> Indexsearcher and the reader.
>
> Then also i am not able to delete the file in windows
>
> Do i have to close anything other than the indexsearcher and the reader to
> delete the files
>
>
> On 2/1/06, Howie Wang <[EMAIL PROTECTED]> wrote:
> >
> > I haven't tested this out too well, but I've been using it on my
> > development box. In case people are wondering how to get a
> > new NutchBean which will re-read the index, what I did was write
> > a little JSP page called reset_nutch_bean.jsp. All it does it remove
> > the "nutchBean" attr from the application context. So the next
> > search that comes along will create a new bean.
> >
> > Any time I upload a new index, I just run this page. Pretty easy.
> > It's not automated, but it's easy enough to do after uploading
> > an index. You could automate it by adding it to a script
> > after finishing an index or after doing an upload or just run it
> > periodically with cron.
> >
> > The code is after my sig. Let me know if what I've done is bad in
> > some way.
> >
> > Howie
> >
> > <%@ page
> > contentType="text/html; charset=UTF-8"
> > pageEncoding="UTF-8"
> >
> > import="javax.servlet.*"
> > import="javax.servlet.http.*"
> >
> > %>
> > <%
> > application.removeAttribute("nutchBean");
> > %>
> >
> >
> >
>
