Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 32877 invoked from network); 2 Mar 2009 11:17:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Mar 2009 11:17:03 -0000 Received: (qmail 39319 invoked by uid 500); 2 Mar 2009 11:17:00 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 39263 invoked by uid 500); 2 Mar 2009 11:16:59 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 39239 invoked by uid 99); 2 Mar 2009 11:16:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2009 03:16:59 -0800 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 torindan@gmail.com designates 209.85.220.168 as permitted sender) Received: from [209.85.220.168] (HELO mail-fx0-f168.google.com) (209.85.220.168) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2009 11:16:52 +0000 Received: by fxm12 with SMTP id 12so2257320fxm.5 for ; Mon, 02 Mar 2009 03:16:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=WqQXjAAZJR+x703zCogyEjJcGchu6930tjfJIi3gEc0=; b=ImFnbAaVX5mjKU/+LZNHM9mLZxTXEt0TIBYbvxl9uY9fQBrblHn+ehgEDO4UFwa+hk ypBY4/6T1Th2ImNDVrDvHrM9ACrZ5A7fYPTlQ+kvR66JsbXENEmSiDu9DVc+Z2jayK2E XRMNMcFUJW78CwtoZDcMNC7Q4+A5N8BjtEjDI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=OucxhxtmFfNgh97TxwbeQ00M1C8B4EOhl+4PAz56ju8A9C06UKi1MHvq1s+I6Ad3s5 WmFFVKV+6aeT+yCySa9dfLsMCQAtsQyAF02dwAnEUbV2uOfqmTwkV1L1Nn1+NegD3ZPT 6RPlpdo92ZFzPOTET6+O4N36KdEIi36xlXt30= MIME-Version: 1.0 Received: by 10.181.217.2 with SMTP id u2mr2082719bkq.153.1235992589976; Mon, 02 Mar 2009 03:16:29 -0800 (PST) In-Reply-To: References: <49A354DC.30907@gmail.com> <3304BABA-2441-4369-BF53-0FE7FF593B5B@mikemccandless.com> <49A6DEC9.7050600@gmail.com> <92C633F7-0DF2-449B-B30B-3826A017C1D1@mikemccandless.com> <49A82DAD.5060103@gmail.com> <691FBA1C-69E8-4B9C-A9AE-97D00E3DBA34@mikemccandless.com> <2ffb6d060903012342h177c67eage4541637028e4ad9@mail.gmail.com> Date: Mon, 2 Mar 2009 13:16:29 +0200 Message-ID: <2ffb6d060903020316o548a91dfodb008c0b3c2a2e11@mail.gmail.com> Subject: Re: segments.gen file From: =?UTF-8?B?RGFuaWwgxaJPUklO?= To: java-dev@lucene.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org I'm more interested in reopen(IndexCommit) so I could have full benefits of LUCENE-1483 (faster open, warm caches, less GC and so on) but on specific commit point. I'm not sure it's possible in current trunk, and if we have open(IndexCommit) & company, maybe we should also have similar set of methods for reopen? On Mon, Mar 2, 2009 at 12:12, Michael McCandless wrote: > > This is already available, as of 2.4. > > Mike > > Danil =C5=A2ORIN wrote: > >> What about opening IndexReader/Searcher on certain commit point? >> Will it be implemented in 2.9? >> >> The use-case is similar to the one Michael Busch described, only I >> would like to open (or reopen) a searcher on specific commit point. >> >> >> On Fri, Feb 27, 2009 at 20:31, Michael McCandless >> wrote: >>> >>> Michael Busch wrote: >>> >>>> Actually I personally don't need Lucene to be "write once". The reason >>>> why >>>> I started this thread about the segments.gen file was that in our >>>> project we >>>> sometimes need to rollback to a previous commit-point (using Lucene >>>> 2.4.0) >>>> that we keep around with the SnapshotDeletionPolicy. To get rid of the >>>> newest commit-point we simply delete the most recent segments file. Bu= t >>>> then >>>> we also have to delete the segments.gen file, otherwise Lucene will re= ad >>>> the >>>> generation from it and try to find the segments file we deleted. Then >>>> Lucene >>>> will recreate the segments.gen file. This just made me think that this >>>> is >>>> not very clean (deleting and recreating the segments.gen) especially >>>> because >>>> we use a local FS and don't even need the .gen file. >>> >>> Ahh... OK. =C2=A0In trunk/2.9, you can explicitly open an IndexWriter o= n a >>> prior >>> commit point, which will take care of the gen file for you. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org >> For additional commands, e-mail: java-dev-help@lucene.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-dev-help@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org