Eric Louvard wrote:
my problem is that IndexWriter.optimize() take 20 minutes. OK it is not
a lot of time, but I can't allow me to block the system such a long time
:-(.
If you're worried about blocking, queue changes to the index and have a
separate thread which processes the queue, adding a
t: Re: IndexWriter.optimize() need to much time.
Of course I can acces IndexReader, but I need to acces IndexWriter during
optimization.
If I am using a 'temp-index' I need to merge it with the optimized index how
can I do it ?
Thanks.
Éric
Mordo, Aviran (EXP N-NANNATEK) wrote:
The ind
ginal Message-
From: Eric Louvard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 05, 2005 10:27 AM
To: java-user@lucene.apache.org
Subject: Re: IndexWriter.optimize() need to much time.
Of course I can acces IndexReader, but I need to acces IndexWriter during
optimization.
If I am using a
you can do indexing in separate thread keeping waiting documents in some
kind of queue waiting to be indexed.
Eric Louvard wrote:
Of course I can acces IndexReader, but I need to acces IndexWriter
during optimization.
If I am using a 'temp-index' I need to merge it with the optimized
index ho
Of course I can acces IndexReader, but I need to acces IndexWriter
during optimization.
If I am using a 'temp-index' I need to merge it with the optimized index
how can I do it ?
Thanks.
Éric
Mordo, Aviran (EXP N-NANNATEK) wrote:
The index is available for search even during optimization,
Just use 2 different indices? One temp one that is being optimized and one
current being used. Then switch the paths on your application when the temp
one is ready.
- Original Message -
From: "Eric Louvard" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 05, 2005 3:10 PM
Subject: IndexWr
The index is available for search even during optimization, you should not have
any problem with that.
Aviran
http://www.aviransplace.com
-Original Message-
From: Eric Louvard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 05, 2005 10:10 AM
To: java-user@lucene.apache.org
Subject: I
