e: Wed, 1 Aug 2007 13:14:04 -0400> From: [EMAIL PROTECTED]> To:
> java-user@lucene.apache.org> Subject: Re: IndexReader deletes more that
> expected> On 8/1/07, Ridwan Habbal <[EMAIL PROTECTED]> wrote:>> but what
> about runing it on mutiThread app like web appli
tandardAnalyzer, true);indexWriter.close();}
> Subject: RE: IndexReader deletes more that expected> Date: Wed, 1 Aug 2007
> 09:07:32 -0700> From: [EMAIL PROTECTED]> To: java-user@lucene.apache.org> >
> If I'm reading this correctly, there's something a littl
> Subject: RE: IndexReader deletes more that expected> Date: Wed, 1 Aug 2007
> 09:07:32 -0700> From: [EMAIL PROTECTED]> To: java-user@lucene.apache.org> >
> If I'm reading this correctly, there's something a little wonky here. In>
> your exa
On 8/1/07, Ridwan Habbal <[EMAIL PROTECTED]> wrote:
>
> but what about runing it on mutiThread app like web application? There
> you are the code:
If you are targeting a multi threaded webapp than I strongly suggest you
look into using either Solr or the LuceneIndexAccessor code. You will want
ject: IndexReader deletes more that expected
Hi, I got unexpected behavior while testing lucene. To shortly address
the problem: Using IndexWriter I add docs with fields named ID with a
consecutive order (1,2,3,4, etc) then close that index. I get new
IndexReader, and call IndexReader.deleteDoc
Hi, I got unexpected behavior while testing lucene. To shortly address the
problem: Using IndexWriter I add docs with fields named ID with a consecutive
order (1,2,3,4, etc) then close that index. I get new IndexReader, and call
IndexReader.deleteDocuments(Term). The term is simply new Term("ID
