Hi,
I am using lucene in our site for index and search. We are creating the
index with large collection of documents (XML). The program some times
terminating without completing the index process. So the index optimization
and closing is not properly done. Is it to be optimized on the next index
Hi,
How exactly is your application terminating? Is there an error? An exception?
If so, please provide the stack trace to get a better/right answer.
No, the index is not automatically optimized at the beginning of indexing.
There are likely no issues with documents that were already indexed
Hi,
Thanks for the response. The error is probably related with mysql. My
appliation using mysql for keeping the status of indexed documents. So that
duplication can be avoided. Some times the mysql connection has been lost,
and the program terminated.
Sonu
On 6/25/07, Otis Gospodnetic [EMAIL
In this case, it seems that everything is under your control and you
can gracefully close the Lucene index down when this occurs. Which
I would recommend under any circumstances so as to insure that you
know the state of your index.
At issue here is whether the last N documents that you've
That seems to be the correct usage. Can you provide a self contained
unit test showing what you are doing or, at least, more supporting code?
-Grant
On Jun 24, 2007, at 5:14 PM, Lee Li Bin wrote:
Hi,
May I know how do I store TermVector?
When I set the last parameter to true, isn't
Is this repeatable?
Is it, possibly, over NFS (or other file sharing)?
What versions of Lucene, JDK, what OS?
Is it, possibly Lucene 2.0 on Linux with Java 1.5? (In this case see
http://256.com/gray/docs/misc/java_bad_file_descriptor_close_bug.shtml)
Btw, when starting a new discussion please do
thanks Erick.
On 6/25/07, Erick Erickson [EMAIL PROTECTED] wrote:
In this case, it seems that everything is under your control and you
can gracefully close the Lucene index down when this occurs. Which
I would recommend under any circumstances so as to insure that you
know the state of your