Mailing-List: contact general-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <42F8E095.7030806@apache.org>
Date: Tue, 09 Aug 2005 09:57:57 -0700
From: Doug Cutting <cutting@apache.org>
User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720)
MIME-Version: 1.0
To: general@lucene.apache.org
Subject: Re: IndexWriter and IndexReader open at the same time
References: <50a1290508081614182cafe@mail.gmail.com>
	 <20050809012404.92921.qmail@web31104.mail.mud.yahoo.com>
 <50a129050808202373e58539@mail.gmail.com>
In-Reply-To: <50a129050808202373e58539@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Greg Love wrote:
> In the TheServerSide case study of the book, page 375, they say that
> they close the IndexWriter and even point out that they did before
> openning the IndexReader and deleting. So that kinda makes me wonder
> if i'm safe having an IndexReader with deletions and and IndexWriter
> with inserts open at the same time (even though my code never does an
> index modifying operation at the same time because they share a lock
> in the my code).

You should close the IndexReader you are using for deletions before 
opening the IndexWriter you use for additions.  For higher throughput, 
queue additions and deletions and process them periodically as batches. 
  If you're concerned about an addition followed by a deletion of the 
same document getting reversed in the queues, then simply check the 
addition queue each time you queue a deletion, and remove any matching 
additions.

Doug