From java-user-return-46985-apmail-lucene-java-user-archive=lucene.apache.org@lucene.apache.org Tue Aug 10 18:20:49 2010 Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 7248 invoked from network); 10 Aug 2010 18:20:49 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Aug 2010 18:20:49 -0000 Received: (qmail 29104 invoked by uid 500); 10 Aug 2010 18:20:47 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 28977 invoked by uid 500); 10 Aug 2010 18:20:46 -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 28969 invoked by uid 99); 10 Aug 2010 18:20:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 18:20:46 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of IKoelliker@axsone.com designates 204.142.131.82 as permitted sender) Received: from [204.142.131.82] (HELO pubsrv03.ctronsoft.com) (204.142.131.82) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 18:20:40 +0000 X-TM-IMSS-Message-ID: Received: from mailsrv1.ctronsoft.com ([10.0.5.50]) by axsone.com ([204.142.131.82]) with ESMTP (TREND IMSS SMTP Service 7.0) id bab9a1c6000013a6 ; Tue, 10 Aug 2010 14:14:50 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Index merge question Date: Tue, 10 Aug 2010 14:16:09 -0400 Message-ID: <33814FB2B9C8164294DF032B686739F99E0394@mailsrv1.ctronsoft.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Index merge question Thread-Index: Acs4pRHZ2XLCW6OxRmSzJXMaFEbb3gAEmOqA References: <33814FB2B9C8164294DF032B686739F99E0391@mailsrv1.ctronsoft.com> From: To: X-TM-AS-Product-Ver: IMSS-7.0.0.6352-6.0.0.1038-17334.004 X-TM-AS-Result: No--8.768-5.0-31-1 X-imss-scan-details: No--8.768-5.0-31-1 Would it matter if an IndexReader was opened while an index merge is in progress? Thanks -----Original Message----- From: Erick Erickson [mailto:erickerickson@gmail.com]=20 Sent: Tuesday, August 10, 2010 12:03 PM To: java-user@lucene.apache.org Subject: Re: Index merge question When you open an IndexReader, Lucene effectively takes a "snapshot" of the index and searches it until you reopen your reader. So the timing of when the merged index gets used is up to you, so you should be fine. Best Erick On Tue, Aug 10, 2010 at 11:28 AM, wrote: > Hello, > > Is there any point during a merge operation where the index cannot be > searched or is unstable? We want to create a bunch of smaller indexes in > parallel and then merge them into a single index that may have searches > running against it. > > > > Thanks, > > Ian Koelliker > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org