Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@apache.org Received: (qmail 58273 invoked from network); 20 Aug 2003 23:00:37 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 20 Aug 2003 23:00:36 -0000 Received: (qmail 8713 invoked by uid 97); 20 Aug 2003 23:03:10 -0000 Delivered-To: qmlist-jakarta-archive-lucene-user@nagoya.betaversion.org Received: (qmail 8702 invoked from network); 20 Aug 2003 23:03:10 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 20 Aug 2003 23:03:10 -0000 Received: (qmail 85300 invoked by uid 500); 20 Aug 2003 22:31:11 -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 85119 invoked from network); 20 Aug 2003 22:31:07 -0000 Received: from rwcrmhc12.comcast.net (216.148.227.85) by daedalus.apache.org with SMTP; 20 Aug 2003 22:31:07 -0000 Received: from lucene.com (12-210-200-74.client.attbi.com[12.210.200.74](untrusted sender)) by comcast.net (rwcrmhc12) with SMTP id <20030820222317014002sanoe>; Wed, 20 Aug 2003 22:23:17 +0000 Message-ID: <3F43F4D3.3020007@lucene.com> Date: Wed, 20 Aug 2003 15:23:15 -0700 From: Doug Cutting User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lucene Users List Subject: Re: Will failed optimize corrupt an index? References: <4A46E75D51A2D5119F2A00B0D03D7F09010B8BD4@exchange.hq.openratings.com> In-Reply-To: <4A46E75D51A2D5119F2A00B0D03D7F09010B8BD4@exchange.hq.openratings.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N The index should be fine. Lucene index updates are atomic. Doug Dan Quaroni wrote: > My index grew about 7 gigs larger than I projected it would, and it ran out > of disk space during optimize. Does lucene have transactions or anything > that would prevent this from corrupting an index, or do I need to generate > the index again? > > Thanks! > > --------------------------------------------------------------------- > 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