Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 82850 invoked from network); 1 Jul 2008 10:48:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Jul 2008 10:48:03 -0000 Received: (qmail 66245 invoked by uid 500); 1 Jul 2008 10:47:58 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 65755 invoked by uid 500); 1 Jul 2008 10:47:58 -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 65744 invoked by uid 99); 1 Jul 2008 10:47:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2008 03:47:57 -0700 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 shalinmangar@gmail.com designates 209.85.198.232 as permitted sender) Received: from [209.85.198.232] (HELO rv-out-0506.google.com) (209.85.198.232) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2008 10:47:07 +0000 Received: by rv-out-0506.google.com with SMTP id f6so1909846rvb.5 for ; Tue, 01 Jul 2008 03:47:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=giJNvBrHMPI2tKyDd7BTxgxcZr88hUAS91CoMU4OIYU=; b=dViYq8XdHkDDLAhPqtzMqPibNRXzRlZCB7syGl9Of35XNbOsRqFjkAEmdivEg/d8f/ w/LDxwcp29WgsjQGXO3Yk9IwVRdA9d3zN7hICJXio5OIRkulyjBNvOzOGnhSv3MhPBDO IjE7hSpm6oO02aiiBC2GadfLYVZwPEEnbQDfk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=KIDUSIV20L+dfmV4h8fMz/hMdpTpPKjMY7ZHcFpvGBTs+R4r+SYreTB5sdbQE5GPK6 pczebXcSKFHxiiiKoqROGHTz+KFreIoUit7XP56gugzY3YoNLE3+uqRK9GmBAoSWnhlq fhWxauqloH2+YJgaeKmcOf7pBtK9E52bPCT0g= Received: by 10.141.205.10 with SMTP id h10mr3397612rvq.54.1214909247848; Tue, 01 Jul 2008 03:47:27 -0700 (PDT) Received: by 10.140.178.17 with HTTP; Tue, 1 Jul 2008 03:47:27 -0700 (PDT) Message-ID: <69de18140807010347s6269fea5r12c3212e0ec0a12a@mail.gmail.com> Date: Tue, 1 Jul 2008 16:17:27 +0530 From: "Shalin Shekhar Mangar" To: java-user@lucene.apache.org Subject: IndexDeletionPolicy and optimized indices MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm implementing a custom IndexDeletionPolicy. An IndexCommit object does not have any information whether it's index is optimized or not. How can a IndexDeletionPolicy know which IndexCommit instances corresponded to optimized indices? -- Regards, Shalin Shekhar Mangar. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org