ne works.
Thanks,
Adam
----------------
> Date: Wed, 20 Dec 2006 22:11:33 -0500
> From: [EMAIL PROTECTED]
> To: java-user@lucene.apache.org
> Subject: Re: Rebuilding index on a regular basis
>
> Hi,
>
> How about this:
>
> 1) You copy the files that make
e.apache.org
> Subject: Re: Rebuilding index on a regular basis
>
> Hi,
>
> How about this:
>
> 1) You copy the files that make your index in a new folder
> 2) You update your index in that new folder (forcing if necessary, old locks
> will not be valid)
> 3) When
Hi Erick,
Thanks for the suggestion of using 2 indexes. The number of documents is small
- about 2000, and it builds quickly - about 3s from a database. I am currently
trying to rebuild every 2 minutes, but could probably reduce that to 5. That
could be as long as 10 minutes, but that's ab
Hi,
How about this:
1) You copy the files that make your index in a new folder
2) You update your index in that new folder (forcing if necessary, old locks
will not be valid)
3) When update is completed, close your readers, and open them on the new
index.
4) Copy the fresh index files to the pre
Why not switch where the searchers look rather than copy the index and
restart? That is, your searcher is pointing at index1, and you build the new
one in a a new dir (index2). On some signal, your server closes the searcher
pointing to index1 and opens one pointing to index2 and uses that until
t
Note: I have changed the title of this thread to match its content
I am currently facing a similar issue. I am dealing with a large index
that is constantly used and needs to be updated on a daily basis. For
fear of corruption I would rather rebuild the index each time,
performing tests against
