Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@apache.org Received: (qmail 39766 invoked from network); 29 Jul 2003 23:37:17 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 29 Jul 2003 23:37:17 -0000 Received: (qmail 22019 invoked by uid 97); 29 Jul 2003 23:39:59 -0000 Delivered-To: qmlist-jakarta-archive-lucene-user@nagoya.betaversion.org Received: (qmail 22012 invoked from network); 29 Jul 2003 23:39:58 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 29 Jul 2003 23:39:58 -0000 Received: (qmail 39451 invoked by uid 500); 29 Jul 2003 23:37:14 -0000 Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Users List" Reply-To: "Lucene Users List" Delivered-To: mailing list lucene-user@jakarta.apache.org Received: (qmail 39438 invoked from network); 29 Jul 2003 23:37:14 -0000 Received: from mail.disney.com (204.128.192.15) by daedalus.apache.org with SMTP; 29 Jul 2003 23:37:14 -0000 Received: from Hermes10.corp.disney.com (hermes10.corp.disney.com [153.7.110.102]) by mail.disney.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id h6TNFQri007264 for ; Tue, 29 Jul 2003 16:36:34 -0700 (PDT) Received: from sm-cala-xc04.swna.wdpr.disney.com by hermes.corp.disney.com with ESMTP; Tue, 29 Jul 2003 16:37:33 -0700 Received: from sm-cala-xm11.swna.wdpr.disney.com ([153.7.195.53]) by sm-cala-xc04.swna.wdpr.disney.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 29 Jul 2003 16:37:18 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Safe to write while optimizing? Date: Tue, 29 Jul 2003 16:37:18 -0700 Message-Id: <496A2C679221504D8B8AE4B10267E876019D7AB9@gb-sm-cala-xm11.corp.disney.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Safe to write while optimizing? Thread-Index: AcNWGEP+wTVJTvDQSVKgSzuNa8zujAAEd/TA From: "Wilton, Reece" To: "Lucene Users List" X-OriginalArrivalTime: 29 Jul 2003 23:37:18.0946 (UTC) FILETIME=[59AA6420:01C3562A] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thanks for the reply. =20 Just to clarify: You are saying that I can optimize and add a document at the same time as long as both threads use the same IndexWriter. Is that correct? -----Original Message----- From: Doug Cutting [mailto:cutting@lucene.com]=20 Sent: Tuesday, July 29, 2003 2:27 PM To: Lucene Users List Subject: Re: Safe to write while optimizing? Wilton, Reece wrote: > Three questions: > - Is it safe to have two IndexWriters open on the same index? No. It is not safe, and the code makes every attempt to prohibit it. > - Is it safe to have two IndexWriters adding a document concurrently? No, but you can have two threads adding documents to a single=20 IndexWriter concurrently. > - Is it safe to add a document while another IndexWriter is optimizing > the index? No, but, so long as you use a single IndexWriter object, synchronization should handle things correctly so that one thread can add documents=20 while another optimizes. Doug --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-user-help@jakarta.apache.org