Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of jason.rutherglen@gmail.com
 designates 209.85.198.232 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:references;
        b=MqrGu5NCKjQ+hoE3erfL8D9XoCOnFQL7Lf0FuEX0YDD14+Y+QzDqPx/UEzIiyfbR76
         cOeiwVI8UVX+ggLE9ujfgGMUWyyFt5Hyl5RllX0lgGWZbTF8Q1JaE5sr28u5svDonQWX
         L7ptm2D7ryn3q9bcHVm5gAhWY5HTUPGdpW5UA=
Message-ID: <85d3c3b60806221306j67a549b6g74b159794c69654a@mail.gmail.com>
Date: Sun, 22 Jun 2008 16:06:47 -0400
From: "Jason Rutherglen" <jason.rutherglen@gmail.com>
To: java-dev@lucene.apache.org
Subject: Re: ReaderCommit
In-Reply-To: <C2B079C5-B3DD-4BDB-A710-3BEFD624990B@mikemccandless.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_19936_2028137.1214165207609"
References: <85d3c3b60806220609j3efb7421pc863c79d8ac3a3ca@mail.gmail.com>
	 <C2B079C5-B3DD-4BDB-A710-3BEFD624990B@mikemccandless.com>

------=_Part_19936_2028137.1214165207609
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

For Ocean I created a workaround where the IndexCommits from
IndexDeletionPolicy are saved in a map in order to achieve deleting based on
the IndexReader.  It would be more straightforward to delete from the
IndexCommit in IndexReader.  I realize people want to get away from
IndexReader performing updates, however, for my use case, realtime search
updating from IndexReader makes sense mainly for obtaining the doc ids of
deletions.  With IndexWriter managing the merges it would seem difficult to
expose doc numbers, but perhaps there is a way.

On Sun, Jun 22, 2008 at 3:30 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:

>
> Jason Rutherglen wrote:
>
>  Is there a reason ReaderCommit in DirectoryIndexReader.getIndexCommit()
>> does not support delete?
>>
>
> I think we are getting away from using IndexReader to make changes to the
> index, so, I didn't want to enable deleting a commit point from IndexReader.
>
>  Is is proper behavior to use SnapshotDeletionPolicy and then keep the
>> IndexCommit around?
>>
>
> Likely not really.  If you intend to keep the commit around indefinitely
> you should use a better matched deletion policy that keeps track, over time,
> of what should not be deleted.  EG SnapshotDeletionPolicy does not save to
> disk which commit points are still held open.
>
>  What is the difference where the former does not support delete?
>>
>
> Not sure what you're asking here?
>
> Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>

------=_Part_19936_2028137.1214165207609
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

For Ocean I created a workaround where the IndexCommits from IndexDeletionPolicy are saved in a map in order to achieve deleting based on the IndexReader.&nbsp; It would be more straightforward to delete from the IndexCommit in IndexReader.&nbsp; I realize people want to get away from IndexReader performing updates, however, for my use case, realtime search updating from IndexReader makes sense mainly for obtaining the doc ids of deletions.&nbsp; With IndexWriter managing the merges it would seem difficult to expose doc numbers, but perhaps there is a way.&nbsp; <br>
<br><div class="gmail_quote">On Sun, Jun 22, 2008 at 3:30 PM, Michael McCandless &lt;<a href="mailto:lucene@mikemccandless.com">lucene@mikemccandless.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
Jason Rutherglen wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is there a reason ReaderCommit in DirectoryIndexReader.getIndexCommit() does not support delete?<br>
</blockquote>
<br></div>
I think we are getting away from using IndexReader to make changes to the index, so, I didn&#39;t want to enable deleting a commit point from IndexReader.<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is is proper behavior to use SnapshotDeletionPolicy and then keep the IndexCommit around?<br>
</blockquote>
<br></div>
Likely not really. &nbsp;If you intend to keep the commit around indefinitely you should use a better matched deletion policy that keeps track, over time, of what should not be deleted. &nbsp;EG SnapshotDeletionPolicy does not save to disk which commit points are still held open.<div class="Ih2E3d">
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
What is the difference where the former does not support delete?<br>
</blockquote>
<br></div>
Not sure what you&#39;re asking here?<br>
<br>
Mike<br>
<br>
---------------------------------------------------------------------<br>
To unsubscribe, e-mail: <a href="mailto:java-dev-unsubscribe@lucene.apache.org" target="_blank">java-dev-unsubscribe@lucene.apache.org</a><br>
For additional commands, e-mail: <a href="mailto:java-dev-help@lucene.apache.org" target="_blank">java-dev-help@lucene.apache.org</a><br>
<br>
</blockquote></div><br>

------=_Part_19936_2028137.1214165207609--