Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: domain of yseeley@gmail.com designates
 64.233.166.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=ktZbxCfyN7UkTfqQVMOHz5IRVnLyVT4BftqZrRVKjpFeD3u4jMiWTZZ4fV0qn4XjI3/fk5gsbY4/wvUWyMQVDz9YZ0FTiTwJwkCED1Q/qvmZc/HVmdkV6/uqcSiolou2ycIVtJoOWa2rq2p+lJqEfpznPASEeNUHLIjIJ2BKoKk=
Message-ID: <c68e39170609131949o31548c37m1c1d54670a5f4eb9@mail.gmail.com>
Date: Wed, 13 Sep 2006 22:49:15 -0400
From: "Yonik Seeley" <yonik@apache.org>
Sender: yseeley@gmail.com
To: java-dev@lucene.apache.org
Subject: Re: [jira] Commented: (LUCENE-665) temporary file access denied on
 Windows
In-Reply-To: <c68e39170609131947s792c562cg695fc0003ea95e07@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <E1F190DAC247C64FAA46B38316FA151D04D99C76@EX-101.mail.navisite.com>
	 <4508722B.3010202@mikemccandless.com>
	 <c68e39170609131420o5e1067cfja96029db99c4d1f@mail.gmail.com>
	 <Pine.LNX.4.58.0609131452200.25120@hal.rescomp.berkeley.edu>
	 <4508809C.4000204@mikemccandless.com>
	 <c68e39170609131742g733456b8t189748540ca752b@mail.gmail.com>
	 <4508BE24.8050600@mikemccandless.com>
	 <c68e39170609131947s792c562cg695fc0003ea95e07@mail.gmail.com>

On 9/13/06, Yonik Seeley <yonik@apache.org> wrote:
> On 9/13/06, Michael McCandless <lucene@mikemccandless.com> wrote:
> > Yonik Seeley wrote:
> > >> But, I'm still renaming segments_N.new -> segments_N,
> > >
> > > Hmmm, remind me why you need the .new file?  Why can't you just create
> > > segments_N after you are finished writing all of the segments?
> >
> > Because there could be a reader that tries to read the file before it's
> > done being written.  It would hit EOF and throw an IOException.
>
> Ahh, right... unlikely (the segments file is pretty small), but possible.
>
> Another alternative (since this changes the index format anyway) is to
> put something in the segments file to detect if it's partially
> written... something like the size of the file or the number of
> segments.  I don't know if the extra complexity would be worth saving
> the creation time of an extra file or not...

Hey wait... the segments file already has the number of segments.
Can't you tell if it's not yet complete?

-Yonik

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org