o,
> use that one to add your docs, else, open a new one and store it in a
> central place where the next message to come in can go and find it?
>
> Each instance of IndexWriter is thread safe, so it's fine if multiple
> threads add documents at the same time.
>
>
e, it should not try to open a 2nd IndexWriter while a
> previous one is still working on a previous message).
>
> Mike
>
> Sandeep K wrote:
>
>>
>> Thanks a lot Mike,
>> There will be only one machine which uses IndexWriter and its the
>> JMS
help
thanks and regards,
Sand
Sandeep K wrote:
>
> Hi all..
> I had a question related to the write locks created by Lucene.
> I use Lucene 2.3.2. Will this newwer version create locks while indexing
> as older ones?
> or is there any other way that lucene handles its opera
Thanks a lot Mike,
There will be only one machine which uses IndexWriter and its the
JMS server. This server will first create the file in the physical file
system(its Linux)
and then index the saved file.
Michael McCandless-2 wrote:
>
>
> Sandeep K wrote:
>
>>
>
Hi all..
I had a question related to the write locks created by Lucene.
I use Lucene 2.3.2. Will this newwer version create locks while indexing as
older ones?
or is there any other way that lucene handles its operations?
And my another doubt is that i use JMS for lucene indexing.
My App server w
