Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of shalinmangar@gmail.com
 designates 209.85.198.227 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=KHcNaN1pgFO2JiBzqxzZd8c+E5y4qxs9GcCffRrZBK+JxaNxgBPM3rnfBvLcBqvhnA
         LcDMMLbU+IyyXNPftXQ3JOZUCrUGzENDgximTq/Fw2Tizdu3LzgzipW7OnjPnRydfUrl
         OljxlYvP6WDXxW0FT0YJZCSZECwHRKvr2ooZQ=
Message-ID: <69de18140807020217q2ab1c3c3se1cb33a4099f3a6c@mail.gmail.com>
Date: Wed, 2 Jul 2008 14:47:24 +0530
From: "Shalin Shekhar Mangar" <shalinmangar@gmail.com>
To: java-user@lucene.apache.org
Subject: Re: IndexDeletionPolicy and optimized indices
In-Reply-To: <F21AB543-C901-4043-8569-2976EAEEB903@mikemccandless.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <69de18140807010347s6269fea5r12c3212e0ec0a12a@mail.gmail.com>
	 <F21AB543-C901-4043-8569-2976EAEEB903@mikemccandless.com>

Hi Michael,

Thanks for the response.

Looking at the general way the filenames are organized:

IndexCommit.getFileNames() without optimize (after IW.close())
[segments_4, _0.cfs, _1.cfs, _2.cfs]
IndexCommit.getFileNames() after optimize+close [segments_5, _4.cfs]

We can compare the latest commit point's files with the previous
commit point's files and if the number of .cfs files have decreased
(or equal) (with a +1 in generation number), can we reliably say if an
optimize has happened?

On Tue, Jul 1, 2008 at 5:44 PM, Michael McCandless
<lucene@mikemccandless.com> wrote:
>
> You're right IndexCommit doesn't know that it represents an optimized index.
>
> Likewise, IndexCommit doesn't know other "semantic" things about the index, eg, you've just called expungeDeletes, or, you just finished adding batch X of documents to the index, etc.
>
> Also, realize that with autoCommit=false (to be the only choice in 3.0), no commit will be done after an optimize.  Ie you have to call commit() or close() explicitly to make it a commit.
>
> I think the simplest general approach to "know" which commit points represent "interesting" times to the application would be to call IW.optimize() then IW.commit() (if you are using trunk) or just IW.close(), then look at the last IndexCommit passed to your deletion policy's onCommit() and record yourself that this commit was the result of an optimize.
>
> Mike
>
> Shalin Shekhar Mangar wrote:
>
>> 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
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>


--
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