On Friday 29 September 2006 22:28, Mark Modrall wrote:
> So is IndexModifier opening an IndexReader when someone calls .delete()
> then closing the reader and opening an IndexWriter when someone calls
> addDocument() (for example)?
If someone calls delete and the reader is not open yet, it opens
your system. Thank you.
-Original Message-
From: Daniel Naber [mailto:[EMAIL PROTECTED]
Sent: Friday, September 29, 2006 2:46 PM
To: java-user@lucene.apache.org
Subject: Re: IndexModifier and finding records
On Friday 29 September 2006 14:54, Mark Modrall wrote:
> It
> would be n
On Friday 29 September 2006 14:54, Mark Modrall wrote:
> It
> would be nice if I could do IndexSearcher(IndexModifier) or
> IndexSearcher(IndexModifier.getReader()) or something.
The reader and writer are closed automatically if needed, so they cannot
easily be given to the outside. If you want
Hi...
I was just looking at the IndexModifier class, which seems
like a nice consolidation for some of our operations. There is one
question I have though. The class says that it internally contains an
IndexReader and an IndexWriter and has examples of operations doing
both. But
