From java-user-return-14750-apmail-lucene-java-user-archive=lucene.apache.org@lucene.apache.org Mon Jun 06 17:22:59 2005 Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 89458 invoked from network); 6 Jun 2005 17:22:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Jun 2005 17:22:59 -0000 Received: (qmail 32020 invoked by uid 500); 6 Jun 2005 17:22:50 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 31979 invoked by uid 500); 6 Jun 2005 17:22:49 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 31946 invoked by uid 99); 6 Jun 2005 17:22:49 -0000 X-ASF-Spam-Status: No, hits=4.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,FORGED_YAHOO_RCVD,FROM_ENDS_IN_NUMS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from web32107.mail.mud.yahoo.com (HELO web32107.mail.mud.yahoo.com) (68.142.207.121) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 06 Jun 2005 10:22:45 -0700 Received: (qmail 14247 invoked by uid 60001); 6 Jun 2005 17:22:28 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=qX5EyyBMtIx0RsjG9+15Cd+vmxsueveNxcBBaD8HW7XfroM1ZAS5uDDDxHbiMfsK7L5aOnvYOuFLAifbndVc4bo6Tz8eSgjf13Ij32HeVAFT5URtL01UmAlhPSxNJ+579qodS8j/QBNCxGSPyEN/qjzWLjbnvdRf+F/AwKg90fA= ; Message-ID: <20050606172228.14245.qmail@web32107.mail.mud.yahoo.com> Received: from [206.13.63.69] by web32107.mail.mud.yahoo.com via HTTP; Mon, 06 Jun 2005 10:22:28 PDT Date: Mon, 6 Jun 2005 10:22:28 -0700 (PDT) From: Aalap Parikh Subject: Re: searches and updates concurrency problem To: java-user@lucene.apache.org In-Reply-To: <42A41A69.7060407@blizzy.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, As per my understanding of Lucene, I think concurrent search and update to an index should not corrupt the index, given that only a single index-modifying operation is executing at any point of time. So in short, you can have multiple search operations and not more than one index update (add and/or delete) operation in progress at any time and that should not corrupt the index. Thanks, Aalap. --- Maik Schreiber wrote: > > My problem is that the index update procedure and > the searches could run > > simultaneously, and, if they do, they corrupt the > index file. > > Is there a way to let Lucene handle this > concurrency automatically (like > > stop the searches till the update is finished)? > > Lucene does not handle this by itself but relies on > outside synchronization. > You might want to have a look at LuceneIndexAccessor > (please see > http://issues.apache.org/bugzilla/show_bug.cgi?id=34995) > > -- > Maik Schreiber * http://www.blizzy.de > > GPG public key: > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x1F11D713 > Key fingerprint: CF19 AFCE 6E3D 5443 9599 18B5 5640 > 1F11 D713 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: > java-user-help@lucene.apache.org > > __________________________________ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org